Cause: com.sap.engine.interfaces.messaging.api.exception.MessagingException: java.io.IOException: Can't parse the document; HTTP 200 OK

[former_member251814]

Hi All,

I am facing issue with ICO scenario SOAP to Proxy (Soap receiver with XI 3.0 protocol) . We recently deployed support pack in PI 7.30 from SP04 to SP12.

Message is sent with External soap header to PI.Error i am facing is below:

This works fine in non patched envioronment. Anybody faced similar issues? Please help!!

Cause: com.sap.engine.interfaces.messaging.api.exception.MessagingException: java.io.IOException: Can't parse the document; HTTP 200 OK

message.Information	SOAP: Processing completed
message.Information	SOAP: Response message leaving the adapter
message.Information	Message status set to DLNG
message.Information	Executing Request Mapping "urn.HydroOne.com:CS4:SCHDUpdatePCAD_069:PI/OM_SCHDUpdate_BEA_to_ECC" (SWCV e92a7450a72f11e08a29f11b8e0a15e3)
message.Information	Delivering to channel: CC_Receiver_XI_xxx_AAE_xxx
message.Information	MP: processing local module localejbs/sap.com/com.sap.aii.af.soapadapter/XISOAPAdapterBean
message.Information	SOAP: Request message entering the adapter processing with user J2EE_GUEST
message.Information	SOAP: Target url: http://xxxx:xxxx/sap/xi/engine?type=entry
message.Error	SOAP: Call failed: java.io.IOException: Cant parse the document; HTTP 200 OK
message.Error	SOAP: Error occurred: com.sap.engine.interfaces.messaging.api.exception.MessagingException: java.io.IOException: Cant parse the document; HTTP 200 OK
message.Error	MP: exception caught with cause com.sap.engine.interfaces.messaging.api.exception.MessagingException: java.io.IOException: Cant parse the document; HTTP 200 OK
message.Error	Exception caught by adapter framework: java.io.IOException: Cant parse the document; HTTP 200 OK
message.Error	Transmitting the message to endpoint <local> using connection SOAP_http://sap.com/xi/XI/System failed, due to: com.sap.engine.interfaces.messaging.api.exception.MessagingException: java.io.IOException: Cant parse the document; HTTP 200 OK
message.Information	Message status set to WAIT
message.Information	The asynchronous message was successfully scheduled to be delivered at Mon Jun 08 10:54:39 EDT 2015
message.Information	Message status set to TBDL
message.Error	Could not consume message from the queue, due to: Error retrieving message from database store. Reason: Could not create Message. Reason: com.sap.engine.interfaces.messaging.api.exception.MessagingException: Could not parse XMBMessage due to Cant parse the document
message.Information	The asynchronous message was successfully scheduled to be delivered at Mon Jun 08 10:59:39 EDT 2015
message.Information	Message status set to WAIT
message.Information	Message status set to TBDL

Regards,

Swapnil

[iaki_vila]

HI Swapnil,

Check if the path sap/xi/engine?type=entry is available in the SICF ECC transaction.

Regards.

[rcsegovia]

Hi,

See blow link and open separate thread in 

cheers,

Roberto.