cancel
Showing results for 
Search instead for 
Did you mean: 

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

Former Member
0 Kudos

Hi guys

   We faced one issue in SOAP to SOAP scenario at PI 7.31 Single stack java system. We did all the configurations to receive the message from partner PI system using below type URL's. This scenario is like pass thru without any mapping, Just sharing some text data from partner system.

   When data will pushing from Partner system, It showing success at partner end. But Target end data will not reach and also not showing any entry in message monitor tab.

   But in system log it showing the below SAX parsing error. So please guide us and share your valuable comments to resolve the same.


#2.0 #2013 09 02 13:08:05:369#+0700#Error#com.sap.aii.af.sdk.xi.util.StreamXMLScannerImpl#
#BC-XI-CON-AFW#com.sap.aii.af.lib#C000AC1E89A919BA00000001000018A4#7347450000000004#sap.com/com.sap.aii.adapter.soap.app#com.sap.aii.af.sdk.xi.util.StreamXMLScannerImpl.open()#ZPIAPPLPOZ#490##470E44DD139211E3B07A000000701CFA#470e44dd139211e3b07a000000701cfa#470e44dd139211e3b07a000000701cfa#0#Thread[HTTP Worker [@318554728],5,Dedicated_Application_Thread]#Plain##
Caught an Exception: org.xml.sax.SAXParseException: Content is not allowed in prolog.#

#2.0 #2013 09 02 13:08:05:370#+0700#Error#com.sap.aii.af.sdk.xi.mo.Message#
#BC-XI-CON-AFW#com.sap.aii.af.lib#C000AC1E89A919BA00000002000018A4#7347450000000004#sap.com/com.sap.aii.adapter.soap.app#com.sap.aii.af.sdk.xi.mo.Message.reparseRootDocument()#ZPIAPPLPOZ#490##470E44DD139211E3B07A000000701CFA#470e44dd139211e3b07a000000701cfa#470e44dd139211e3b07a000000701cfa#0#Thread[HTTP Worker [@318554728],5,Dedicated_Application_Thread]#Plain##
Error during parsing the SOAP part --- Can't parse the document#

Thanks in advance

Vijaykumar.S

Accepted Solutions (0)

Answers (1)

Answers (1)

iaki_vila
Active Contributor
0 Kudos

Hi Vijaya,

Check this Shabarish Vijayakumar's  blog http://scn.sap.com/community/pi-and-soa-middleware/blog/2012/08/16/the-mystery-of-content-is-not-all..., it could be helpful for you.

Also, the problem could be:

1. Sintaxis error in the XML

2. The XML contains a BOM

Regards,

Former Member
0 Kudos

Dear Vila,

      This is for pass thru scenario and sharing some text data from partner system using SOAP URL. Target side No mapping used.

Thanks

Vijayakumar S

iaki_vila
Active Contributor
0 Kudos

Hi Vijaya,

In the blog there are two possible solutions, Shabarish said that you can remove the SWCV reference in the receiver determination and the sender agreement, later Stephen Grube said that if you choose the service interface like XI 3.0 compatible will resolve the problem as well.

Regards.

markangelo_dihiansan
Active Contributor
0 Kudos

Hello Vijaya,

Please check if Note 1786611 - Namespace definitions missing in payload is applicable to you. The symptoms are since the namespaces are removed, it fails at adapter engine level. It cannot be remedied using java/xslt mapping.

Hope this helps,

Mark