Skip to Content
avatar image
Former Member

Problem with XML file format after server upgrade - XML not well formed


we experice problems in one of our interfaces, apperaring after a server upgrade from Windows to Linux (at location of sender service).

The file sent into XI gives a "XML not well formed" exception and I wonder how to get around this. Look at the example files below. The first one looks strange, but I don't know why the file is generated in this way. Any input would be helpful...

The sxmb_moni gives this error description:

  <SAP:P1>Problem extracting values from the message: The exception occurred (program: CL_SWF_RLS_CONDITION==========CP, include CL_SWF_RLS_CONDITION==========CM00Q, line: 161)</SAP:P1> 

<SAP:Stack>Error when determining the receiver: Problem extracting values from the message:

When I look at the XML file itself it gives: "XML not well formed"

The file looks like the following after the upgrade:

Content-Type: application/xop+xml; charset=UTF-8; type="text/xml";
Content-Transfer-Encoding: binary
Content-ID: <root.message at>

<soap:Envelope xmlns:soap=""><soap:Body><ns1:   ........ etc

Before the upgrade the file looked like:

<?xml version="1.0" encoding="utf-8"?><env:Envelope xmlns:env="" env:encodingStyle="" xmlns:types="" xmlns:xsi="" xmlns:xsd="" ><env:Body ><tns:



Add comment
10|10000 characters needed characters exceeded

  • Follow
  • Get RSS Feed

1 Answer

  • Nov 29, 2010 at 02:57 PM

    I know there was an issue with a low SP level in PI 7.1

    Maybe you look out for a patch or report to SAP.

    Add comment
    10|10000 characters needed characters exceeded