Missing faultcode; HTTP 200 OK

[Former Member]

Hi Experts,

we received following message from SOAP receiver adapter. Can anyone asisst me?

- <SAP:Error SOAP:mustUnderstand="1" xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">

<SAP:Category>XIAdapterFramework</SAP:Category> 

<SAP:Code area="MESSAGE">GENERAL</SAP:Code>

<SAP:P1 />

<SAP:P2 />

<SAP:P3 />

<SAP:P4 />

<SAP:AdditionalText>com.sap.engine.interfaces.messaging.api.exception.MessagingException: java.io.IOException: Missing faultcode; HTTP 200 OK</SAP:AdditionalText>

<SAP:Stack />

<SAP:Retry>M</SAP:Retry>

</SAP:Error>

i tested via SOAPUI successfully.

Kind Regards,

PM

[baskar_gopalakrishnan2 · Accepted solution]

Very similar your issue is already in this thread.   As  Michal said you can see the server log on the webservice side to see more details. 

http://scn.sap.com/thread/1255067

[Former Member · Accepted solution]

sorry but we have no access on WS side. Any suggestions?

[markangelo_dihiansan · Accepted solution]

Hello Peter,

What does the raw tab say for the response message? Is it returning an empty http body?

Regards,

Mark

[Former Member · Accepted solution]

Please find below soap UI reponse;

HTTP/1.1 200 OK

Content-Length: 540

Content-Type: text/xml

Server: Microsoft-IIS/7.5

X-Powered-By: ASP.NET

<?xml version="1.0"?>

<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/">

     <SOAP-ENV:Body SOAP-ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/">

         <NS1:Response xmlns:NS1="urn:Status">

             <return xsi:type="xsd:string">code ok</return>

         </NS1:Response>

     </SOAP-ENV:Body>

</SOAP-ENV:Envelope>

[markangelo_dihiansan · Accepted solution]

Hello Peter,

The return looks like an RPC-Encoded request rather than document-literal. The SOAP Receiver adapter by default uses document-literal, so build your request using Java/XSLT mapping by checking the Do Not Use SOAP Envelope option in the CC. Also use MessageTransformBean to set the correct content-type (by using Do Not Use SOAP Envelope, the content-type defaults to application/xml).

You would also need Java/XSLT mapping to parse the response.

Hope this helps,

Mark