Skip to Content
author's profile photo Former Member
Former Member

WD JCO SSO ticket not working


The following error message keeps following me:$Exception: (102) JCO_ERROR_COMMUNICATION: JCO.Client not connected in repository call

This message gets displayed when I push the test button of a newly created JCO Connection.

The WD application in question uses two JCO Connections who connect to the same SAP backend system.

The JCO for metadata which is set to use usr/pwd logon method does work, however the one which is set to use ticket (saplogonticket) doesn´t.

The fact that the other JCO works tells me that SLD configuration is correct, as a matter of fact the ping-test of the problematic JCO also works.

I´m logged on to the WD Content Administrator with a username which is also present on the backend so that shouldn´t be the problem either.

Another thing I find strange is that the exception group "JCO_ERROR_COMMUNICATION" will occur in case of some system unavailability due to network/gateway/router issue.

But if that´s the case than the other JCO test should also fail.

On top of that I checked if host / port was known and this also had possitive outcome.


ping [/code]

One thing I could do is set the trace level of JRFC/JCO/JRA, like described in

SAP Java Connector Problem Analysis Scenarios

but its not possible to use the configtool anytime soon because a request should be made to the technical team.

Another thing I was thinking that this could be a incompatibility issue?

  • J2EE WAS (JCO) is 7.0SP9 (NW2004s)

  • SLD also 7.0SP9

  • and the backend system: ECC5.0 WAS 6.40SP18

I checked Product Availability Matrix but didn´t find anything, as yet.

Anyone familiar with this?

Any suggestions?

What does "Client not connected in repository call" mean?


Add a comment
10|10000 characters needed characters exceeded

Assigned Tags

Related questions

1 Answer

  • author's profile photo Former Member
    Former Member
    Posted on Jan 05, 2007 at 05:35 PM

    I also made sure a logonticket was created by using a http analyzer tool.

    A cookie with name "MYSAPSSO2" does appear.

    Another thing that puts me of is the output of transaction SLDCHECK on the backend system.

    Testing the RFC connection to the SLD java client ...
    RFC ping returned exception with message:
    Error opening an RFC connection.
    Summary: Connection to SLD does not work
    => Check SLD function and configurations

    But I guess this could only be problematic for XI?

    If not how should I correct this?


    Add a comment
    10|10000 characters needed characters exceeded

    • Former Member Former Member

      Hi Valery,

      thanks again.

      /message/2842807#2842807 , like I said I´m pretty sure that authentication is not the cause... because the same user/credentials is used as in the old situation...

      But I guess if it would be the cause then it would also become clear from the traces/logs were I can evaluate the tickets being accepted.

      So again, can anyone guide me through howto get this information from the backend please?

      Regards, Wim.

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.