Soap error 'Bad envelope tag: definitions'

[mtremblay-savard]

Hi everyone,

I am currently doing some tests on web services going through PI and I got stuck upon an error that I can't find the cause. I am sending a synchronous web service using SOAP UI that goes to SAP PI, which maps it to my SAP ECC web service and then comes back. I am using SOAP for both request and response.

When I look into SXMB_MONI, both the resquest and the response shows as red(error) with this error message: com.sap.engine.interfaces.messaging.api.exception.MessagingException: org.xml.sax.SAXException: Bad envelope tag: definitions

My quality of service is set to Best effort in both ways. When I tried the Only Once option, the call did not show any error but I never received any response either.

If anyone has an idea on what could actually cause this issue, i'd be glad to hear it.

Thanks!

[mtremblay-savard]

Thanks guys for the reply.

Using the payload of the request call adapter, I am able to call the SAP ECC web service directly from soap ui, instead of going through PI.

Here's my payload:

If I take this, and put it in my soap request like this:

My SAP ECC web service respond perfectly:

When going through PI, the response doesn't even have a payload at all. The request has the error message but only in the response message:

I hope these additional information can help. Thanks for the support!

[bhavesh_kantilal]

Hello Maxime,

Can you check the Error Logs in ECC in transaction SRT_UTIL?

What I think is happening is : That the request that goes out from PI is not what your webservice accepts and hence the same fails and returns the error back to PI.

The Error Log Button in SRT_UTIL will contain the Errors and hopefully we find some logs here that begin to make sense.

Regards,

Bhavesh

[mtremblay-savard]

Hi Bhavesh,

Unfortunately there are no error log when calling the web service through PI. I tested using SOAP UI to call directly the SAP ECC web service including an error and the message showed up. But that's the only error message i can see there.

[bhavesh_kantilal]

To me it looks to be the case with the response. While both the request and response messages show error it is to show that the entire message is in error. In reality as the asynch went through to PI, it seems to be the case where when the response comes over from ECC something goes wrong.

Can you check which step there error is in? Share more details on the error message from Trace?

In all likelihood it could be the response XML being invalid or mapping failing but would need more info to look further.

Regards

Bhavesh

[mtremblay-savard]

Hi Bhavesh,

Where can I see which step is in error? The complete error message I see in SXMB_MONI is this one:

What's weird is that the SOAP Body Manifest of my response only contains this:

[former_member186851]

Hello Maxime,

Seems to be a data issue.

Check the payload if the tags are well formatted.

Get the payload from monitoring and test it in mapping, wrong tags can be identified.

[Former Member]

it looks the test message you are using is not in correct format/invalid. Try test with valid xml message.