on 11-05-2012 11:27 PM
Hi Experts
We are on a project to upgrade PI7.0 to PI7.3. Currently we are facing an issue in SOAP adapter in PI7.3 where all interfaces are failing due to error -
Error in Plain Http Adapter Processing
The detailed error log is as follows -
<SAP:Error SOAP:mustUnderstand="1" xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
<SAP:Category>XIAdapter</SAP:Category>
<SAP:Code area="PLAINHTTP_ADAPTER">ATTRIBUTE_SERVER</SAP:Code>
<SAP:P1>500</SAP:P1>
<SAP:P2>Error during parsing of SOAP header</SAP:P2>
<SAP:P3><SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/"> <SOAP:Header> </SOAP:Header> <SOAP:Body> <SOAP:Fault xmlns:SOAP="SOAP:ClientError" _mce_href="http://schemas.xmlsoap.org/soap/envelope/"><faultcode>SOAP:Client</faul... during parsing of SOAP header</faultstring><faultactor>http://sap.com/xi/XI/Message/30</faultactor><detail><SAP:Error SOAP:mustUnderstand="1" xmlns:SAP="XIProtocolhttp://sap.com/xi/XI/Message/30"><SAP:Category>XIProtocol</SAP:Category><SAP:Code area="PA...
<SAP:P4 />
<SAP:AdditionalText />
<SAP:Stack>HTTP server code 500 reason Error during parsing of SOAP header explanation <SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/"> <SOAP:Header> </SOAP:Header> <SOAP:Body> <SOAP:Fault xmlns:SOAP="SOAP:ClientError" _mce_href="http://schemas.xmlsoap.org/soap/envelope/"><faultcode>SOAP:Client</faul... during parsing of SOAP header</faultstring><faultactor>http://sap.com/xi/XI/Message/30</faultactor><detail><SAP:Error SOAP:mustUnderstand="1" xmlns:SAP="XIProtocolhttp://sap.com/xi/XI/Message/30"><SAP:Category>XIProtocol</SAP:Category><SAP:Code area="PARSER">ITEM_MISSING</SAP:Code><SAP:P1>{http://schemas.xmlsoap.org/soap/envelope/}Envelope</SAP:P1><SAP:P2/><SAP:P3/><SAP:P4/><SAP:AdditionalText/><SAP:ApplicationFaultMessage namespace=""/><SAP:Stack>XML element {http://schemas.xmlsoap.org/soap/envelope/}Envelope missing in SOAP message header (SAP XI Extension) </SAP:Stack></SAP:Error></detail></SOAP:Fault> </SOAP:Body> </SOAP:Envelope></SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Have you come across this error in any scenarios? if yes, please help me with the solution.
Regards
Vikas
thanks for your response guys. The issue of error in plan HTTP adapter was that that the adpater between PI & ECC system was set as HTTP adapter and not XI adapter.
Now we have another issue, when the data comes in from the third party through SOAP sender channel, the channel shows up as successful but the message doesn't reach Integration server. In the Message Monitoring, for component adapter engine, the messages are showing as successful for request (third party to ERP) and response (ERP to third party) but there is no message in integration server. What could be the reason that mesages can't be seen in integration server, neither there is any evidence of message getting into ERP system. The SOAP sender synchronous channel is set with Adapter Engine as Central Adapter Engine.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Any mor inputs friends?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
If I understand correctly, you are getting error in SOAP adapter with protocol HTTP...
check the channel setting , is it having use envelop checked ?, as the error suggest envelop missing...
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello Vikas,
I think you are using Plain HTTP Adapter instead of SOAP Adapter. Can you recheck this? Can you tell us more about your scenario?
Regards,
Mark
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Mark
We are using SOAP adapter. These are synchronous interfaces from third party system to ECC system via PI. Source system has stored the WSDL files of the interfaces in their system. These files were provided to them from the PI7.0 system (long ago). We think that the WSDL files should remain unchanged as there is no change in the Data structure of the interfaces. The Interface objects were exported from PI7.0 and imported into PI7.3.
None of these interfaces are working and it seems that all the issues are due to same error in the SOAP adapter (not sure which error) - Error in Plain Http Adapter Processing
Please let me know if you need more information.
Regards
Vikas
User | Count |
---|---|
98 | |
11 | |
11 | |
10 | |
10 | |
8 | |
6 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.