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

SLD problem with transaction SLDCHECK


I am configuring XI 3.0Sr1 to worK with SLD on Netweaver 04 stack 10, everything is good until I come to test the connection with the transaction SLDCHECK.

What happens is that a browser window is displayed with the SLD server address in the address bar, but no content. The XI check passes successfully.

Having debugged the transaction the prblem seems to lie within the call to a function module "SLDJAVA_ACCESSOR_REQUEST" at RFC destination "SAPSLDAPI".

the function module returns with a sy-subrc of 8 and the following message in the s-msgv1 - 4 parameters.

"AbapSLDRequestHandler.execEnumerateInstances(): Invalid begin of response [expected: 'HTTP', found:'´###############ö###9Packet length (1347375956) bigger than the max specified!ö####ö###Yjavax.jms.J尀倀爀"

The SLD communicates correctly using RZ10 and I have set up the connection in SLDAPICUST.

Does anybody have any idea what the problem might be as I am running out of ideas.

Thanks in advance


Add a comment
10|10000 characters needed characters exceeded

Assigned Tags

Related questions

2 Answers

  • Best Answer
    Posted on Jan 24, 2005 at 09:39 AM

    Hi Edward,

    please verify that your setup using a standalong SLD is as follows. Let's assume that your XI SR1 system is A and the SLD is B. The RFC Destination LCRSAPRFC on A must point to A - this destination is used for accessing the Exchange Profile. The Destination SAPSLDAPI on A must point to B - this destination is used for accessing the SLD.

    Kind regards,


    Add a comment
    10|10000 characters needed characters exceeded

    • Former Member

      Hi Andreas,

      Managed to solve the problem. It was something really simple that I spotted when I went back through each step of the XI installation guide.

      In SLDAPICUST I had the port number for the SLD as 51110 rather than 51100. Took me ages to notice the extra "1".



  • Posted on Jan 19, 2005 at 08:54 AM

    Hello Ed,

    did you use the unicode flags for the destination SAPSLDAPI and the rfc connection in the visual admin?

    To which J2EE Engine do the destinations LCRSAPRFC and SAPSLDAPI point to?

    Kind regards,


    Add a comment
    10|10000 characters needed characters exceeded

    • Former Member Former Member


      I have just set up a new connection to the 6.40 J2EE engine from R/3 Enterprise, creating new destinations in both the Visual Administrator and in SM59.

      SLDCHECK work flawlessly from R/3 Enterprise 6.20 non unicode. It still doesn't work from NW04 unicode to the J2EE engine.

      Anybody have any ideas.


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.