DeliveryException:invalid content type for SOAP: TEXT/HTML

[Former Member]

Hi All,

When i am testing WSDL with XML spy i am getting correct response.

I am getting following error in syn-Receiver-SOAP Adapter.

I checked Proxy & user authentications ID &password it is correct.

I tried to create datatype & by importing WSDL but still same error.

I also tried to copy past the XML send by XI from SXMB_MONI into XML-SPY, xml-spy still sending data successfully.

Also one more strange behaviour I observe that XML-SPY not asking any Proxy and user authentications ID & password for posting data in web-service.

Please guide what can I do? I tried all the ways in previous forms.

<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>

- <!-- Call Adapter

-->

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

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

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

<SAP:P1 />

<SAP:P2 />

<SAP:P3 />

<SAP:P4 />

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

<SAP:ApplicationFaultMessage namespace="" />

<SAP:Stack />

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

</SAP:Error>

Regards

[Former Member · Accepted solution]

Hi,

Try the same WSDL with SOAPSONAR its works fine and its also asks authentication also....

and you can track error better in the SOAPSONAR...

Amaresh

[Former Member]

closed

[moorthy]

HI,

Did you check this thread discussion-

Ignore this if you have already applied.

Regards,

Moorthy

[Former Member]

Hi Krishna,

I am can post data by xml-spy & SAP-BC with same WSDL & URL.

URL i am using is -"https://clientsqa.cartus.com/eaf/eaf.asp"

And when i am opening this in e-explorer I am getting following(WM team is saying that this the message what XI should send):

<?xml version="1.0" ?>

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

- <SOAP-ENV:Body>

- <SOAP-ENV:Fault>

<faultcode>SOAP-ENV:Server</faultcode>

<faultstring>Server Error</faultstring>

- <detail>

<message>XML document must have a top level element.</message>

</detail>

</SOAP-ENV:Fault>

</SOAP-ENV:Body>

</SOAP-ENV:Envelope>

<b>But my WSDL is as follows</b>

<?xml version="1.0" encoding="UTF-8"?>

<!-- Generated 02/14/02 by Microsoft SOAP Toolkit WSDL File Generator, Version 1.02.813.0 -->

<definitions name="WebServiceAuthorization" targetNamespace="http://tempuri.org/wsdl/" xmlns:wsdlns="http://tempuri.org/wsdl/" xmlns:typens="http://tempuri.org/type" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:stk="http://schemas.microsoft.com/soap-toolkit/wsdl-extension" xmlns="http://schemas.xmlsoap.org/wsdl/">

<types>

<schema targetNamespace="http://tempuri.org/type" xmlns="http://www.w3.org/2001/XMLSchema" xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" elementFormDefault="qualified"/>

</types>

<message name="clsSubmitAuth.Authorization">

<part name="ClientNo" type="xsd:string"/>

<part name="FormID" type="xsd:short"/>

</message>

<message name="clsSubmitAuth.AuthorizationResponse">

<part name="Result" type="xsd:string"/>

</message>

<portType name="clsSubmitAuthSoapPort">

<operation name="Authorization" parameterOrder="ClientNo FormID">

<input message="wsdlns:clsSubmitAuth.Authorization"/>

<output message="wsdlns:clsSubmitAuth.AuthorizationResponse"/>

</operation>

</portType>

<binding name="clsSubmitAuthSoapBinding" type="wsdlns:clsSubmitAuthSoapPort">

<stk:binding preferredEncoding="UTF-8"/>

<soap:binding style="rpc" transport="http://schemas.xmlsoap.org/soap/http"/>

<operation name="Authorization">

<soap:operation soapAction="http://tempuri.org/action/clsSubmitAuth.Authorization"/>

<input>

<soap:body use="encoded" namespace="http://tempuri.org/message/" encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"/>

</input>

<output>

<soap:body use="encoded" namespace="http://tempuri.org/message/" encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"/>

</output>

</operation>

</binding>

<service name="WebServiceAuthorization">

<port name="clsSubmitAuthSoapPort" binding="wsdlns:clsSubmitAuthSoapBinding">

<soap:address location="https://clientsqa.Cartus.com/eaf/eaf.asp"/>

</port>

</service>

</definitions>

[Former Member]

Hi All,

We are using NTLM authontication. Can any one help wheather XI can work with NTLM or not?

If not then what changes to be made in NTLM authontication to make work XI with web-service?

Because as per thread Xi can not work with NTLM authontication.

Regards

[bhavesh_kantilal]

Rohan,

take a look at Stefan Grube's reply in this thread,

Regards,

Bhavesh

[Former Member]

Hi Bhavesh,

I already tried to use this but no progress.

Thanks for hint.

Regards

[moorthy]

Hi,

Can you try the SOAP Adapter configuration once again and check it out..probably something would have missed ...

Just try if any luck..

Hope your Webservice is working fine...also your wsdl structure is also valid one - i,e after mapping before it calls to Webservice

Regards,

Moorthy

[Former Member]

Hi Krishna,

Thanks for reply.

My configurations in SOAP Receiver Adapter is as follows

Target URL - https://clientsqa.Cartus.com/eaf/eaf.asp

Configure User Authentication - X

User , password (clients)

Configure Proxy - X

Host, Port

Configure Proxy user Authentication - X

User, password (our network)

SOAP Action - http://tempuri.org/action/clsSubmitAuth.Authorization

I think for above posted WSDL theas information is correct in adapter.

Regards

[Former Member]

Hi All,

One more behaviour that when i am checking Do not use SOAP envelope option then I am able to see successfull devivered flag in SXMB_MONI.

But in that case i am getting "You are not authorized to view this page HTTP 401.1 - Unauthorized: Logon Failed"

Under SXMB_MONI->second message->Call Adapter->Payloads

(i.e. I am getting HTTP 401.1 in response payload)

Please guide If get any clue.

Regards

[moorthy]

HI,

good to know)

for 401 error, check out option 3 in this blog- /people/krishna.moorthyp/blog/2006/07/23/http-errors-in-xi

Regards,

Moorthy

[Former Member]

hi krishna,

Problem is that. I raised the OSS message for this.

i get the reply that I should not use "Do not use SOAP envelope" option in SOAP receiver adapter. As per information in WSDL.

Regards

[former_member206604]

Hi,

Set the proper content type for a SOAP message it cannot be TEXT/HTML

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

You can use either of these

application/soap+xml

text/plain

text/xml

Regards,

Prakash

[Former Member]

Hi Prakash,

I tried to change content type by following way but still same error.

"change the content type like this: Go to the SOAP receiver communication channel module tab. Add the module "localejbs/AF_Modules/MessageTransformBean" before the standard module. Add the parameter name Transform.ContentType and value text/xml"

Is i am doing correct?

Regards

[former_member206604]

Hi,

Not there.. you need to change it while calling it. I mean from the calling application. The calling application is setting it as HTML.

Regards,

Prakash