Skip to Content
avatar image
Former Member

JCo connection problem : Urgent

Hi ...

I am having a problem while trying to create a JCo connection with Dictionary metadata settings. It gives an RFC error. Can anyone tell me how to rectify this?

Satish.

Add comment
10|10000 characters needed characters exceeded

  • Follow
  • Get RSS Feed

3 Answers

  • avatar image
    Former Member
    Apr 21, 2004 at 05:49 PM

    Satish,

    Here is a solution from Frank Winkler who posted his solution on Apr 21, 2004 2:53 AM. Hopefully this solves your issue. Please see Frank's message attached below:

    -


    frank Winkler

    Posts: 4

    Registered: 3/1/04

    Re: WEB Dynpro JCO connection problem

    Posted: Apr 21, 2004 2:53 AM Reply

    Hi,

    it seems that your JCO-Destinations are not defined in a proper way..

    It is important, that you use two JCO-Destinations;

    one for the Dictionary Data and the other one for the Application-Data.

    You have to define two differnt Destinations, one of Type 'Dictionary Meta Data' and one of Type 'Application Meta Data'. Both point to the same R3 System!

    The first one could access the R3 System only via MessageServer, so you have to take care, that accessing the R3-System via MessageServer must work properly.

    Hope this helps, Frank.

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member Former Member

      Hi

      I think I'm stuck up with the same problem. I seem to be creating both types of connections in the SLD. But when I goto Content Administration, it reports an error saying 'No application servers are maintained in the SLD' and same for the message server.

      What am I missing? Please help me !

      Thanks & Regards,

      Rajit Srinivas.

  • avatar image
    Former Member
    Jul 09, 2004 at 01:15 PM

    Hi Satish,

    I am facing the same problem.Please let me know if you are able solve this issue.It would be great if you can send me the instructions to fix this.

    Add comment
    10|10000 characters needed characters exceeded

    • Hello Russ,

      let's use the SAP Logon Pad to test if you can make a new Connection using the groups function. First login to your MINIWAS 6.2 and start Transaction SMLG and check that you have a valid Logon-Group. More information could be found in the SAP Help at http://help.sap.com/saphelp_webas610/helpdata/en/c4/3a64b4505211d189550000e829fbbd/frameset.htm.

      Then open you SAP Logon Pad and click on the button Groups..., enter the Instance name of your MINIWAS 6.2 System in the Field System-ID and enter the Hostname of your MINIWAS 6.2 System in the Field Message-Server. Then click on create list. Now you should see the Logon Group(s) you just have defined. Click on add and try to connect through this new connection.

      If that is working, also your connection through the Webdynpro Content Administrator should work.

      Regards

      Gregor

  • avatar image
    Former Member
    Jul 12, 2004 at 01:19 PM

    Hello Gregor, thanks for your response.

    As I have posted in another thread....

    My 'services' file has the entry sapmsBSP 3600/tcp with a new line after the entry. I have tried 'PUBLIC' and 'SPACE' both upper and lower and mixed case. Again,

    I go to the SAP Logon pad, click the GROUPS button, enter System ID and message server, then click Generate List, I get a window opening up saying that "Message Server could not find any Groups"

    I see the groups I have created when I return to transaction SMLG, but still can't see them from the stack.

    Any further thoughts?

    Thanks

    Russ

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member Gregor Wolf

      Hi Gregor,

      Can you please tell me the configuration for the message server. I have installed Sneak version 6.40 (90 days trial version). I am totally new to SAP.can you please guide me in this situation. SAP R/3 system installed is configured as a single server. I am not able to find the message service sapms<SID> on that system when i am trying to connect.

      Thanks,

      Mital.