cancel
Showing results for 
Search instead for 
Did you mean: 

Error in SOAP Receiver

arunneerolil
Contributor
0 Kudos

Hi All,

We are getting the following error with SOAP receiver adapter.

<SAP:Error>

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

<SAP:Code>MESSAGE.GENERAL</SAP:Code>

<SAP:AdditionalText>com.sap.aii.af.ra.ms.api.DeliveryException: invalid content type for SOAP: TEXT/HTML</SAP:AdditionalText>

</SAP:Error>

Can anyone help.

Thanks in Advance

Chemmanz

Accepted Solutions (1)

Accepted Solutions (1)

Shabarish_Nair
Active Contributor
0 Kudos

>>>com.sap.aii.af.ra.ms.api.DeliveryException: invalid content type for SOAP

As the message says i guess your SOAP request is not what is expected by the Wenservice .. do recheck the same. Maybe you can test it idependently via XML Spy.

Ref:

/people/shabarish.vijayakumar/blog/2008/01/08/troubleshooting--rfc-and-soap-scenarios-updated-on-20042009

/people/shabarish.vijayakumar/blog/2006/03/23/rfc--xi--webservice--a-complete-walkthrough-part-1

/people/shabarish.vijayakumar/blog/2006/03/28/rfc--xi--webservice--a-complete-walkthrough-part-2

Answers (3)

Answers (3)

stefan_grube
Active Contributor
0 Kudos

The response of the Webservice is not SOAP-XML, you recive an HTML document instead.

This can happen when:

- your URL is wrong. Test it with a web browser

- the user has not sufficient authority to use the web service.

- you need a proxy server in your SOAP adapter config.

Regards

Stefan

Former Member
0 Kudos

Could be that your remote server is returning a normal http error response instead of SOAP, like server busy or something. Worth checking manually or routing through a proxy to debug etc.

Former Member
0 Kudos

Hi Chemmanz,

It looks like you're reaching the outbound binding (i.e. receiver SOAP adapter). Sometimes we get this error either when the target web service is down or is simply unreachable. Double check your Target URL and SOAP Action in the receiver SOAP adapter. Also, your SOAP action should not include quotes.

Also Check the SOAP Address Location in the ESDL file, if you are sending the message to a SOAP Adapter first.

For Ex: <soap:address xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" location="http://<HostName>:port#/XISOAPAdapter/MessageServlet?version=3.0%channel=:<SenderBS>:<SenderCC>"/>

Also go through the steps mentioned in this link, and cross check with what you have done and see if the error is still coming.

/people/siva.maranani/blog/2005/09/03/invoke-webservices-using-sapxi

http://help.sap.com/saphelp_erp2004/helpdata/en/69/a6fb3fea9df028e10000000a1550b0/frameset.htm

http://help.sap.com/saphelp_erp2004/helpdata/en/fc/5ad93f130f9215e10000000a155106/frameset.htm

http://help.sap.com/saphelp_erp2004/helpdata/en/69/a6fb3fea9df028e10000000a1550b0/frameset.htm

Hope they help you solve your problem.

Regards,

Abhy