SLD problem with transaction SLDCHECK

[Former Member]

Hi,

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

Ed.

[andreas_stolz · Accepted solution]

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,

Andreas

[Former Member · Accepted solution]

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".

Regards

Ed

[andreas_stolz]

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,

Andreas

[Former Member]

Hi Andreas,

I must have read your mind as I had just checked that. I had set the unicode flag for the RFC destination on both ends.

Testing in SM59 works as does pressing the unicode test button.

Connected to same box NW04 + ABAP 640 + Java 640 Addon.

Ed

[Former Member]

Hi,

I managed to get the full java error (by using a different browser). The following now appears in the browser window when you rin SLDCHECK.

´?ö9Packet length (1195725856) bigger than the max specified!ööYjavax.jms.JMSException: Packet length (1195725856) bigger than the max specified! at com.sap.jms.protocol.MultiPacketImpl.createPackets(MultiPacketImpl.java:160) at com.sap.jms.protocol.MultiPacketImpl.getNotCompletePacket(MultiPacketImpl.java:106) at com.sap.jms.server.protocol.manager.PacketManagerImpl.processData(PacketManagerImpl.java:77) at com.sap.jms.dispatcher.JMSDispatcherFrame.parseRequest(JMSDispatcherFrame.java:512) at com.sap.engine.core.manipulator.TCPRunnableConnection.sleepRead(TCPRunnableConnection.java:726) at com.sap.engine.core.manipulator.TCPRunnableConnection.run(TCPRunnableConnection.java:527) at com.sap.engine.frame.core.thread.Task.run(Task.java:60) at com.sap.engine.core.thread.impl6.SingleThread.execute(SingleThread.java:72) at com.sap.engine.core.thread.impl6.SingleThread.run(SingleThread.java:142)

Hope somebody know what it means.

Ed

[Former Member]

Ok,

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.

Ed