HTTP 200 error: Error Parsing Response. No XI Response Received

[Former Member]

Dear All,

While running synchronous scenarios from ECC to Legacy System (ECC -> PI 7.11 SP00 -> Legacy) I am getting HTTP 200 error in SXMB_MONI on ECC side. I am unable to receive message in PI system.

Error: Error while receiving by HTTP (error code: 200, error text: Error Parsing Response. No XI Response Received.)

<SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
  <SAP:Category>XIServer</SAP:Category> 
  <SAP:Code area="INTERNAL">CLIENT_RECEIVE_FAILED</SAP:Code> 
  <SAP:P1>200</SAP:P1> 
  <SAP:P2>Error Parsing Response. No XI Response Received.</SAP:P2> 
  <SAP:P3 /> 
  <SAP:P4 />

<SAP:ApplicationFaultMessage namespace="" /> 
  <SAP:Stack>Error while receiving by HTTP (error code: 200, error text: Error Parsing Response. No XI Response Received.)</SAP:Stack> 
  <SAP:Retry>N</SAP:Retry>

While checking the message in SXMB_MONI, I am also unable to see reference of Sender Service in Response message. Probably becuase the message is not reaching PI system.

Many threads mention about checking the mapping but message is not reaching PI server.

I have all RFC connections between ECC and PI and all are working properly. With the same connections and configuration setting all the scenarios are working in QA system.

Please help!!

Thanks and Regards

Chanakya

[Former Member]

Hi Sharma,

In your case we need to test 2 ways. First check whether the response is coming from receiver or not. If it is coming then then the response reaching to PI or not. If you are using soap at the receiver channel simply you can test interface by using soapui. Send the data to the receiver from soap tool. Check whether response is coming to soap tool or not. If you are getting response to the soap tool then you need to check with the PI system .

Regards,

Rama

[Former Member]

@ Stefan: XPA_XIR_CONNECTION is pointing towards PI server and connection is fine.

@Rama: The message is supposed to come from ECC to PI and than PI to Legacy but unfortunately unable to receive message in PI from ECC so no point checking the response from third party legacy system.

Regards

Chanakya

[Former Member]

Issue Resolved.

We were using different user in PI and ECC systems.

In PI system we remove the value dest://XXX_XX_CONNECTION defined under TCode : SXMB_ADM -> Integration Engine Configuration - > Corresponding Integ. Server [leave the value blank]

Also in the same screen click - configuration and set the RUNTIME parameter IS-URL to http://host:port/sap/xi/engine?type=entry and save the setting.

SM59:

Under Logon and security tab PIAPPLUSER user should be used. This user must be maintained in ECC and PI with the same password.

Thanks a lot for the responses.

Regards

[Former Member]

Hi Sharma,

In your case we need to test 2 ways. First check whether the response is coming from receiver or not. If it is coming then then the response reaching to PI or not. If you are using soap at the receiver channel simply you can test interface by using soapui. Send the data to the receiver from soap tool. Check whether response is coming to soap tool or not. If you are getting response to the soap tool then you need to check with the PI system .

Regards,

Rama

[stefan_grube]

Your legacy system does not provide a response.

Check legacy system for the issue.

[Former Member]

Dear Stefan,

I am sorry if my question is not very clear but we are unable to receive message in PI system from ECC.

PI Version: 7.11 SP0

ECC 6.0 Enph 4

Regards

Chanakya

[stefan_grube]

> I am sorry if my question is not very clear but we are unable to receive message in PI system from ECC.

You mean: You do not see messages in PI.

Anyway HTTP 200 means, the message has been processed correctly. No error occurred. So it must have reached any endpoint.

Try to enable sync logging in PI.

> PI Version: 7.11 SP0

This is not a good idea to work with SP0, as many know bugs exist.

[Former Member]

Dear Stefan,

You mean: You do not see messages in PI.

Anyway HTTP 200 means, the message has been processed correctly. No error occurred. So it must have reached any endpoint.

As the scenarios are synchronous we should get some response but unfortunately not. If it is reaching PI than it should be seen in RWB atleast. There are no messages.

Try to enable sync logging in PI.

The Sync_Logging in PI system has been set as 1.

Can it be related to SP issue?

Regards

[stefan_grube]

> Can it be related to SP issue?

I don't know, as I have not worked with SP0, but it is a good idea to apply the latest patch.

Could you confirm in ECC trace, that data are really sent to PI?

[Former Member]

Dear Stefan,

Please find the trace for your reference. The message is getting into error before reaching PI

<?xml version="1.0" encoding="UTF-8" standalone="yes" ?> 
- <!--  Call Integration Server 
  --> 
- <SAP:Trace xmlns:SAP="http://sap.com/xi/XI/Message/30">
  <Trace level="1" type="T">COMMIT is expected by application !</Trace> 
  <Trace level="1" type="B" name="CL_XMS_MAIN-ENTER_XMS" /> 
- <!--  ************************************ 
  --> 
  <Trace level="1" type="B" name="CL_XMS_MAIN-SET_START_PIPELINE" /> 
- <!--  ************************************ 
  --> 
  <Trace level="1" type="B" name="SXMBCONF-SXMB_GET_XMB_USE" /> 
  <Trace level="1" type="B" name="CL_XMS_TROUBLESHOOT-ENTER_PLSRV" /> 
  <Trace level="1" type="T">****************************************************</Trace> 
  <Trace level="1" type="T">* *</Trace> 
  <Trace level="1" type="T">* *</Trace> 
  <Trace level="1" type="T">XMB entry processing</Trace> 
  <Trace level="1" type="T">system-ID = ECP</Trace> 
  <Trace level="1" type="T">client = 400</Trace> 
  <Trace level="1" type="T">language = E</Trace> 
  <Trace level="1" type="T">user = XXXXXX</Trace> 
  <Trace level="1" type="Timestamp">2010-10-05T18:22:31Z INDIA</Trace> 
  <Trace level="1" type="T">* *</Trace> 
  <Trace level="1" type="T">* *</Trace> 
  <Trace level="1" type="T">****************************************************</Trace> 
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_UC_EXECUTE">
  <Trace level="1" type="T">Message-GUID = 4CAB56AD1CA509B8E10000000A823146</Trace> 
  <Trace level="1" type="T">PLNAME = SENDER</Trace> 
  <Trace level="1" type="T">QOS = BE</Trace> 
  <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_SYNC" /> 
- <!--  ************************************ 
  --> 
  <Trace level="1" type="T">Get definition of external pipeline SENDER</Trace> 
  <Trace level="1" type="B" name="CL_XMS_MAIN-LOOKUP_INTERNAL_PL_ID" /> 
  <Trace level="1" type="T">Corresponding internal pipeline SAP_SENDER</Trace> 
  <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST" /> 
  <Trace level="1" type="B" name="PLSRV_CALL_INTEGRATION_SERVER" /> 
- <!--  ************************************ 
  --> 
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
  <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL" /> 
- <!--  ************************************ 
  --> 
- <Trace level="1" type="B" name="CL_XMS_PLSRV_IE_ADAPTER-ENTER_PLSRV">
  <Trace level="1" type="T">URL for integration server read from global configuration</Trace> 
  <Trace level="1" type="T">URL= dest://XPA_XIR_CONNECTION</Trace> 
  <Trace level="1" type="B" name="CL_XMS_PLSRV_CALL_XMB-CALL_XMS_HTTP" /> 
- <!--  ************************************ 
  --> 
  <Trace level="1" type="T">---------------------------------------------------</Trace> 
  <Trace level="1" type="T">SSL not active</Trace> 
  <Trace level="1" type="T">---------------------------------------------------</Trace> 
  <Trace level="1" type="T">HTTP Multipart document length: 4089</Trace> 
  </Trace>
  </Trace>
  <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" /> 
  </Trace>
  <Trace level="1" type="T">SystemError message generated. Guid: 4CAB56BA1CA509B8E10000000A823146</Trace> 
  <Trace level="1" type="T">Error during execution of message : 4CAB56AD1CA509B8E10000000A823146</Trace> 
  <Trace level="1" type="T">ApplicationMessage was (=RefToMsgId): 4CAB56AD1CA509B8E10000000A823146</Trace> 
  <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" /> 
- <!--  ************************************ 
  --> 
  </SAP:Trace>

Regards

[stefan_grube]

Check SM59 if this entry points to PI server:

XPA_XIR_CONNECTION