on 10-24-2013 10:15 AM
Dear Experts,
My scenario is IDOC - PI - SOAP. I am facing the below error in RWB :
The error in RWB is :
23.10.2013 16:48:33.609 | Error | MP: exception caught with cause com.sap.engine.interfaces.messaging.api.exception.MessagingException: SOAP: response message contains an error XIAdapter/PARSING/ADAPTER.SOAP_EXCEPTION - soap fault: GENERAL-0022: Unexpected exception occured: could not execute query |
23.10.2013 16:48:33.609 | Error | Adapter Framework caught exception: SOAP: response message contains an error XIAdapter/PARSING/ADAPTER.SOAP_EXCEPTION - soap fault: GENERAL-0022: Unexpected exception occured: could not execute query |
23.10.2013 16:48:33.609 | Error | Delivering the message to the application using connection SOAP_http://sap.com/xi/XI/System failed, due to: com.sap.engine.interfaces.messaging.api.exception.MessagingException: SOAP: response message contains an error XIAdapter/PARSING/ADAPTER.SOAP_EXCEPTION - soap fault: GENERAL-0022: Unexpected exception occured: could not execute query. |
The transport Protocol is HTTP, Message Protocol is SOAP 1.1
I have referred the below links but its not helpful :
https://scn.sap.com/thread/518981
http://scn.sap.com/thread/182503
Please provide your expert advice on this error.
Thank you,
Merina
Thank you.
HI Merina,
Are you using Query string by any chance? IF so, please uncheck and test.
Regards
Aashish Sinha
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Aashish,
'Use Query String' is in unchecked only.
The Url is : http://<host:port>/wxi/MessageServlet?CommProtocol=SOAP11&CommPartner=PLAIN&MsgClass=IDOC
Thanks,
Merina
Hi Merina ,
You should take the outbound payload xmls that are thowing error and the ones that are not and test it directly with the target URL using SOAP UI or a soap client tool.
You may want to use the wsdl provided by the target application - load it into soap ui and populate with different xmls to look at the details - this appears to be some inconsistent/wrong data going across to your target application which is causing an exception.
Regards
Subhro
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Merina,
There should be some issue with your Outbound Payload and the SOAP Action used in your target URL.
Please check with the third party on the SOAP Action and Target URL.
Thanks and Regards,
Kalyan
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Merina,
Only sometimes the endpoint could be down...
One time i got a similar case and the problem was the asnwer which contained a special characteres ( it came sometimes cyrilic or bulgarian characters), then my question for you, is the error presented always with the same XMLs? if you tried with the same XML throws the exception again?
Regards.
Hi Merina,
That error seems that the endpoint is throwing an error page or similar. Try with SOAPui with the same XML that you are using in the PI test and check if the call is successful.
Regards.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
87 | |
10 | |
10 | |
9 | |
7 | |
6 | |
6 | |
5 | |
4 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.