SAP Knowledge Base Article - Preview

3225646 - Can't parse the document; HTTP 200 error while sending message between Ariba and PI

Symptom

You see error below while sending messages between PI and Ariba:

CLIENT_RECEIVE_FAILED

Configuration error on Adapter-Framework(AFW)-Server

com.sap.engine.interfaces.messaging.api.exception.MessagingException:

com.sap.engine.interfaces.messaging.api.exception.MessagingException: java.io.IOException: Can't parse the document; HTTP 200 ) More details about AFW error can be found in XI monitor MessagingException

In traces, you see similar to below:

Caught an Exception: org.xml.sax.SAXParseException; lineNumber: 1; columnNumber: 15; The prefix "soapenv" for element "soapenv:Body" is not bound.

Error during parsing the SOAP part --- Can't parse the document

Error in parsing response message. 
[EXCEPTION]
Can't parse the document; nested exception caused by: 
Can't parse the document; nested exception caused by: 
org.xml.sax.SAXParseException; lineNumber: 1; columnNumber: 15; The prefix "soapenv" for element "soapenv:Body" is not bound.
at com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.createSAXParseException(ErrorHandlerWrapper.java:204)
at com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.fatalError(ErrorHandlerWrapper.java:178)
at com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:400)
at com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:327)
at com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:284)
at com.sun.org.apache.xerces.internal.impl.XMLNSDocumentScannerImpl.scanStartElement(XMLNSDocumentScannerImpl.java:285)
at com.sun.org.apache.xerces.internal.impl.XMLNSDocumentScannerImpl$NSContentDriver.scanRootElementHook(XMLNSDocumentScannerImpl.java:614)
at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl$FragmentContentDriver.next(XMLDocumentFragmentScannerImpl.java:3132)
at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl$PrologDriver.next(XMLDocumentScannerImpl.java:852)
at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl.next(XMLDocumentScannerImpl.java:602)
at com.sun.org.apache.xerces.internal.impl.XMLNSDocumentScannerImpl.next(XMLNSDocumentScannerImpl.java:113)
at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocumentFragmentScannerImpl.java:505)
at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:842)
at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:771)
at com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser.java:142)
at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.parse(AbstractSAXParser.java:1214)
at com.sun.org.apache.xerces.internal.jaxp.SAXParserImpl$JAXPSAXParser.parse(SAXParserImpl.java:644)
at com.sun.org.apache.xerces.internal.jaxp.SAXParserImpl.parse(SAXParserImpl.java:328)
at javax.xml.parsers.SAXParser.parse(SAXParser.java:196)
at com.sap.aii.af.sdk.xi.util.StreamXMLScannerImpl.open(StreamXMLScannerImpl.java:94)
at com.sap.aii.af.sdk.xi.mo.Message.reparseRootDocument(Message.java:965)
at com.sap.aii.af.sdk.xi.net.MIMEInputSource.readSOAPPart(MIMEInputSource.java:1000)
at com.sap.aii.af.sdk.xi.net.MIMEInputSource.decodePart(MIMEInputSource.java:992)
at com.sap.aii.af.sdk.xi.net.MIMEInputSource.readBody(MIMEInputSource.java:612)
at com.sap.aii.af.sdk.xi.net.MIMEInputSource.parse(MIMEInputSource.java:138)
at com.sap.aii.af.sdk.xi.net.HTTPClientConnection.call(HTTPClientConnection.java:823)
at com.sap.aii.af.sdk.xi.net.HTTPClientConnection.post(HTTPClientConnection.java:314)
at com.sap.aii.af.sdk.xi.srt.CallerServiceImpl2.call(CallerServiceImpl2.java:267)
at com.sap.aii.af.sdk.xi.srt.TransportBubble.onMessage(TransportBubble.java:50)
at com.sap.aii.af.sdk.xi.srt.ExtensionBubble.onMessage(ExtensionBubble.java:64)
at com.sap.aii.adapter.soap.ejb.XISOAPAdapterBean.callBubbleSequenceReceiver(XISOAPAdapterBean.java:1534)
at com.sap.aii.adapter.soap.ejb.XISOAPAdapterBean.process(XISOAPAdapterBean.java:1093)
at sun.reflect.GeneratedMethodAccessor840.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)


Read more...

Environment

  • SAP NetWeaver
  • SAP Process Integration

Product

SAP NetWeaver 7.5

Keywords

Process Integration, PI, Process Orchestration, PO, NetWeaver, XI, AEX, Ariba, error, can't, parse, CLIENT_RECEIVE_FAILED, Configuration, on, Adapter-Framework(AFW)-Server, com.sap.engine.interfaces.messaging.api.exception.MessagingException, java.io.IOException, the, document, HTTP, 200, More, details, about, AFW, can, be, found, in, XI, monitor, MessagingException
, KBA , BC-XI-CON-AFW , J2EE Adapter Framework , Problem

About this page

This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).

Search for additional results

Visit SAP Support Portal's SAP Notes and KBA Search.