Proxy Error in Sender System

[Former Member]

Hello,

we have a scanerio which sends proxy message from ECC to PI system. It has been working fine since last 6 years. Since last few days, it has started coming up with following error in ECC system. Its happening in DEV system and is working ok in prod. I compared DEV and Prod but could not find any difference in proxy code/structure etc. Does anyone please help me on this??? Thanks in advance!

- <!--  Call Integration Server

  -->

- <SAP:Error SOAP:mustUnderstand="1" xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">

  <SAP:Category>XIProtocol</SAP:Category>

  <SAP:Code area="PARSER">ITEM_UNEXPECTED</SAP:Code>

  <SAP:P1><></SAP:P1>

  <SAP:P2><{http://schemas.xmlsoap.org/soap/envelope/}Fault></SAP:P2>

  <SAP:P3 />

  <SAP:P4>ST: ST_XMS_MSGHDR30_SOAP_FAULT</SAP:P4>

  <SAP:AdditionalText />

  <SAP:Stack>Unexpected XML element <>; <{http://schemas.xmlsoap.org/soap/envelope/}Fault> expected System expected the element &#39;{http://schemas.xmlsoap.org/soap/envelope/}Fault&#39;</SAP:Stack>

  <SAP:Retry>M</SAP:Retry>

  </SAP:Error>STR2XSTR

[Former Member · Accepted solution]

Hello All - thanks for your replies. Issue is resolved now. It turned out that somebody in our team changed port and path fix on HTTP connection from ECC to PI. Interesting thing is the error message - totally misleading.

[ManishaRD25]

Hello Dehra,

It seems ECC is receiving response which is not as per expectation / fault message is not handle.

Please check with SOAP team (web service), what is response they are sending? is structure of SOAP response is same as structure created in PI? It looks error at web service side.

Manisha

[Former Member]

Hi Dehra

Is it failing for all the messages you are trying to process or only for a particular message?

It looks like a data issue, its failing because of some special character.

Regards

Osman

[Former Member]

Hello Dehra,

Please check the Payload.

The error says there is some problem with the Payload structure.

Thanks,

Kalyan