PI 7.31 - ITEM_UNEXPECTED

[Former Member]

Hi All,

I have been struggling with getting my ABAB proxy to talk to our PI 7.3 box. When I call the proxy the ABAP completes without error. However in SXMB_MONI the following error exists:

<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>

- <!--

 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>

There doesnt seem to be a load of help on this, however what I have found seems to suggest that my ECC box is trying to communicate to the AAE using SOAP over XI protocol (as detailed in SAP note 1349125) ....

  I am not sure how I can prove if the proxy is trying to communicate over the XI protocol. I know the proxy is using SOAP over HTTP. I can see this in SXMB_ADM.

Any help would be much appreciated as deadlines are rapidly approaching and I have many interfaces I need to get sorted in PI.

Cheers,

Adam

[former_member184720 · Accepted solution]

Did you check this thread?

Make sure that the RFC destination is configured correctly and the connection test is successful.

(sxmb_adm -> runtime(is_url) ) in ECC

[Former Member · Accepted solution]

Yeah, I have checked this. The RFC destination is all set, and connection tests work and return HTTP OK.

Cheers,

Adam

[former_member184720 · Accepted solution]

What is the path prefix in yoru RFC destination?

it should be "/XISOAPAdapter/MessageServlet?ximessage=true"

[Former Member · Accepted solution]

Unfortunatly I dont have authorisation in my client to change this, but at present it is:

/XISOAPAdapter/MessageServlet

The ximessage param isnt set.

Cheers,

Adam

[former_member184720 · Accepted solution]

that could be an issue... may be you can request basis/infra team to get it changed and try testing.

[Former Member · Accepted solution]

I have now got basis to make this change and the error I reported has gone. I am now 1 step further. Unfortunately, its still not working, but the error is an authorisation error that I have passed to basis.

Thanks for your help!

Adam

[former_member184720 · Accepted solution]

The user which you have configured under RFC destination should have the role "SAP_XI_APPL_SERV_USER" assigned in PI

[Former Member · Accepted solution]

The issue was simple. The basis chap forgot to update the password in the RFC user. All is working now.

Cheers,

Adam