cancel
Showing results for 
Search instead for 
Did you mean: 

DeliveryException:: invalid content type for SOAP: TEXT/HTML

Former Member
0 Kudos

Hello,

I try to use an interface RFC -> XI for comunication synchronous with Web Service.

When I execute the RFC the XI receive an error message:

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

<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>

The Traget URL is <a href="http://sdvws.avipam.com.br/InterfaceWS.asmx">http://sdvws.avipam.com.br/InterfaceWS.asmx</a> and SOAP Action is http://tempuri.org/process

Does anybody kown how to solve this issue ?

Regards,

Silvio Galery

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Hi Silvio,

I think the target URL must be the URL to the WSDL. So, if you try putting it in your browser you must see wsdl code. However, when I test the target URL that you post here, I can’t see the WSDL code, but a web page of your webservice! I don’t have sure, but think you don’t need a SOAP action…

I had this problem and I solved it like this ;o)

Cheers,

Ricardo.

Message was edited by: Ricardo Quintino

Former Member
0 Kudos

Thank´s very much. This solved my problem.

Two step for solve this problem

- I change the target URL to the URL?wsdl

- I qualified this URL on the firewall

Cheers,

Silvio.

Former Member
0 Kudos

Hi slivio,

I also have the same problem...so..please give me suggestions.

1. how you changed your URL for WSDl, I also have url, but its not pointing to wsdl file, pointing to some xml code.

2. how did u qualify URL on firewall?

3. Did you use SOAP action?.

Thanks and I appreciate it.

Raj.

Former Member
0 Kudos

Hi Raj, see this my case.

1) I change for this URL http://sdvws.avipam.com.br/InterfaceWS.asmx?wsdl

2) When i put this URL in the browser i don´t see the "page" XML. I get an authorization erro "401 Unauthorized"

3) Yes, I did use the soap action http://tempuri.org/process

Hope this helps,

Regards,

Silvio

Former Member
0 Kudos

Hi silvio and ricardo,

Is the URL posted by Silvio, is it the right one?. I mean is this is the format of Target URL?.

When I paste my <a href="https://clientsqa.cendantmobility.com/eaf/eaf.asp">My Target URL, Plz check it</a> in the browser, I see this,

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>

is this correct?.

Thanks and I appreciate your input,

Raj

Former Member
0 Kudos

Hi Raj,

see this example.

- This is a page the webservice http://webservices.imacination.com/validate/index.jsp

- In this page is the URL of WSDL http://webservices.imacination.com/validate/index.jsp?wsdl.

I think this URL https://clientsqa.cendantmobility.com/eaf/eaf.asp is wrong.

Cheers,

Silvio

Former Member
0 Kudos

HI silvio,

Thanks for the reply. The tow URLs you replied look the same, i dont see the WSDL code in the target URL of the Web service. Could you please confirm it.

So, As soon as you change my web service to target Url, is problem over?

You also told, you qualified the Url on firewall, how did u do that?

Thanks,

Raj.

Former Member
0 Kudos

Hi Raj,

the correct URL is <a href="http://webservices.imacination.com/validate/Validate.jws?wsdl">http://webservices.imacination.com/validate/Validate.jws?wsdl</a>

Please try again.

Cheers,

Silvio.

Former Member
0 Kudos

Hi Raj

Sorry the delay, but I was out of office!

Did you try the link that Silvio gives you? You must see the WSDL code of web service! Something like an XML file but a little bit diferent with some tags like <wsdl:types>... <wsdl:message name>, etc.

Can you provide me more info about your scenario! What kind of scenario do you have? You are trying to invoke a web service from XI?

Post the wsdl link again.

Cheers,

Ricardo.

Message was edited by: Ricardo Quintino

Message was edited by: Ricardo Quintino

Former Member
0 Kudos

Hi Ricardo,

I apologize for my late reply. As I applied OSS Notes, I was waiting for response, but no use.

My Scenario is RFC , XI and Web service Synchronous.

We presently have BC, in which this scenario is working perfect. No problems with target URL.

I am getting the same error Delivery Exception: invalid content type for SOAP:TEXT/HTML.

When I type that URL in the browser, I get some response in XML format.

I dont understand where the problem is: I posted in the forum long ago, but of no use.

If you have any idea let me know.

Thanks,

Raj.

Message was edited by: Raj

Former Member
0 Kudos

Hi Raj,

The web service address that we must type in target URL of receiver soap adapter is the address to the WSDL. To be sure types this address in your browser and you must see a WSDL code of the webservice that you want invoke.

The reason that you are getting “Delivery Exception: invalid content type for SOAP:TEXT/HTML.” is because you are trying to invoke a web service with wrong address.

So, when SOAP receiver adapter try to put the message on the target side, it can’t and automatically receives an HTTP acknowledge in HTML format. As SOAP adapter doesn’t understand HTML code only XML code, it can’t recognize what kind of error is and generates an exception indicating that the content type is invalid.

Delivery Exception: invalid content type for SOAP:TEXT/HTML is equal to any HTTP code, I have almost sure that HTTP code is a 404 Not Found, but you can’t see it...

Post the URL here for I can check

Cheers,

Ricardo.

Former Member
0 Kudos

Hi Ricardo,

Thanks for reply. I searched in the logs, what happening is, it is going to the proxy, getting 200, OK code from proxy. After that I am getting 401, access denied error.

Bcoz they accept the request only from our proxy, so that why its of no use giving you the URL. when I paste that URL in the browser, I get following kind of message.

<?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>

When I contacted the web service guys, they say this is what I am supposed to get.

Since we replacing the existing BC, which is working fine. I dont know why it doesnt work in XI.

If you have any ideas let me know. I appreciate for your input.

Thanks,

Raj.

Former Member
0 Kudos

Hi Raj,

You’re getting a SOAP message fault -> "XML document must have a top level element".

It seams that something are missing on your SOAP request! Something, that gives the ability to receiver SOAP adapter bypass proxy.

Can you place it here the SOAP request?

Cheers,

Ricardo.

Former Member
0 Kudos

Hi Ricardo,

Thanks for your response and help. My file is little bit big, please find it here.

Or you can give me your e-Mail Id!.

The SOAP Request is:

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

<SOAP-ENV:Body>

<m:Authorization xmlns:m="http://tempuri.org/message/" SOAP-ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/">

<ClientNo xsi:type="xsd:string">String</ClientNo>

<FormID xsi:type="xsd:short">4096</FormID>

<UserID xsi:type="xsd:string">String</UserID>

<Password xsi:type="xsd:string">String</Password>

<CustomerFirstName xsi:type="xsd:string">String</CustomerFirstName>

<CustomerMiddleInitial xsi:type="xsd:string">String</CustomerMiddleInitial>

<CustomerLastName xsi:type="xsd:string">String</CustomerLastName>

<CustomerNameSuffix xsi:type="xsd:string">String</CustomerNameSuffix>

<CustomerGender xsi:type="xsd:string">String</CustomerGender>

<SocialInsuranceID xsi:type="xsd:string">String</SocialInsuranceID>

<Comments xsi:type="xsd:string">String</Comments>

<FilePriority xsi:type="xsd:string">String</FilePriority>

<DestinationCityTown xsi:type="xsd:string">String</DestinationCityTown>

<DestinationStateProvince xsi:type="xsd:string">String</DestinationStateProvince>

<DestinationCountry xsi:type="xsd:string">String</DestinationCountry>

<DepartureBusinessTelephone xsi:type="xsd:string">String</DepartureBusinessTelephone>

<DepartureResidenceTelephone xsi:type="xsd:string">String</DepartureResidenceTelephone>

<DestinationBusinessTelephone xsi:type="xsd:string">String</DestinationBusinessTelephone>

<AdditionalTelePhoneType xsi:type="xsd:string">String</AdditionalTelePhoneType>

<AdditionalTelephone xsi:type="xsd:string">String</AdditionalTelephone>

<BusinessEmail xsi:type="xsd:string">String</BusinessEmail>

<DeparturePropertyStreetAddress1 xsi:type="xsd:string">String</DeparturePropertyStreetAddress1>

<DeparturePropertyStreetAddress2 xsi:type="xsd:string">String</DeparturePropertyStreetAddress2>

<DeparturePropertyCityTown xsi:type="xsd:string">String</DeparturePropertyCityTown>

<DeparturePropertyStateProvince xsi:type="xsd:string">String</DeparturePropertyStateProvince>

<DeparturePropertyZipPostalCode xsi:type="xsd:string">String</DeparturePropertyZipPostalCode>

<DeparturePropertyCountry xsi:type="xsd:string">String</DeparturePropertyCountry>

<EffTransferDate xsi:type="xsd:string">String</EffTransferDate>

<Dependent1Relationship xsi:type="xsd:string">String</Dependent1Relationship>

<Dependent1FirstName xsi:type="xsd:string">String</Dependent1FirstName>

<Dependent1MiddleInitial xsi:type="xsd:string">String</Dependent1MiddleInitial>

<Dependent1LastName xsi:type="xsd:string">String</Dependent1LastName>

<Dependent1Gender xsi:type="xsd:string">String</Dependent1Gender>

<Dependent1BirthDate xsi:type="xsd:string">String</Dependent1BirthDate>

<Dependent1AccompanyingDependent xsi:type="xsd:string">String</Dependent1AccompanyingDependent>

<Dependent2Relationship xsi:type="xsd:string">String</Dependent2Relationship>

<Dependent2FirstName xsi:type="xsd:string">String</Dependent2FirstName>

<Dependent2MiddleInitial xsi:type="xsd:string">String</Dependent2MiddleInitial>

<Dependent2LastName xsi:type="xsd:string">String</Dependent2LastName>

<Dependent2Gender xsi:type="xsd:string">String</Dependent2Gender>

<Dependent2BirthDate xsi:type="xsd:string">String</Dependent2BirthDate>

<Dependent2AccompanyingDependent xsi:type="xsd:string">String</Dependent2AccompanyingDependent>

<Dependent3Relationship xsi:type="xsd:string">String</Dependent3Relationship>

<Dependent3FirstName xsi:type="xsd:string">String</Dependent3FirstName>

<Dependent3MiddleInitial xsi:type="xsd:string">String</Dependent3MiddleInitial>

<Dependent3LastName xsi:type="xsd:string">String</Dependent3LastName>

<Dependent3Gender xsi:type="xsd:string">String</Dependent3Gender>

<Dependent3BirthDate xsi:type="xsd:string">String</Dependent3BirthDate>

<Dependent3AccompanyingDependent xsi:type="xsd:string">String</Dependent3AccompanyingDependent>

<Dependent4Relationship xsi:type="xsd:string">String</Dependent4Relationship>

<Dependent4FirstName xsi:type="xsd:string">String</Dependent4FirstName>

<Dependent4MiddleInitial xsi:type="xsd:string">String</Dependent4MiddleInitial>

<Dependent4LastName xsi:type="xsd:string">String</Dependent4LastName>

<Dependent4Gender xsi:type="xsd:string">String</Dependent4Gender>

<Dependent4BirthDate xsi:type="xsd:string">String</Dependent4BirthDate>

<Dependent4AccompanyingDependent xsi:type="xsd:string">String</Dependent4AccompanyingDependent>

<Dependent5Relationship xsi:type="xsd:string">String</Dependent5Relationship>

<Dependent5FirstName xsi:type="xsd:string">String</Dependent5FirstName>

<Dependent5MiddleInitial xsi:type="xsd:string">String</Dependent5MiddleInitial>

<Dependent5LastName xsi:type="xsd:string">String</Dependent5LastName>

<Dependent5Gender xsi:type="xsd:string">String</Dependent5Gender>

<Dependent5BirthDate xsi:type="xsd:string">String</Dependent5BirthDate>

<Dependent5AccompanyingDependent xsi:type="xsd:string">String</Dependent5AccompanyingDependent>

<Dependent6Relationship xsi:type="xsd:string">String</Dependent6Relationship>

<Dependent6FirstName xsi:type="xsd:string">String</Dependent6FirstName>

<Dependent6MiddleInitial xsi:type="xsd:string">String</Dependent6MiddleInitial>

<Dependent6LastName xsi:type="xsd:string">String</Dependent6LastName>

<Dependent6Gender xsi:type="xsd:string">String</Dependent6Gender>

<Dependent6BirthDate xsi:type="xsd:string">String</Dependent6BirthDate>

<Dependent6AccompanyingDependent xsi:type="xsd:string">String</Dependent6AccompanyingDependent>

<Dependent7Relationship xsi:type="xsd:string">String</Dependent7Relationship>

<Dependent7FirstName xsi:type="xsd:string">String</Dependent7FirstName>

<Dependent7MiddleInitial xsi:type="xsd:string">String</Dependent7MiddleInitial>

<Dependent7LastName xsi:type="xsd:string">String</Dependent7LastName>

<Dependent7Gender xsi:type="xsd:string">String</Dependent7Gender>

<Dependent7BirthDate xsi:type="xsd:string">String</Dependent7BirthDate>

<Dependent7AccompanyingDependent xsi:type="xsd:string">String</Dependent7AccompanyingDependent>

<Dependent8Relationship xsi:type="xsd:string">String</Dependent8Relationship>

<Dependent8FirstName xsi:type="xsd:string">String</Dependent8FirstName>

<Dependent8MiddleInitial xsi:type="xsd:string">String</Dependent8MiddleInitial>

<Dependent8LastName xsi:type="xsd:string">String</Dependent8LastName>

<Dependent8Gender xsi:type="xsd:string">String</Dependent8Gender>

<Dependent8BirthDate xsi:type="xsd:string">String</Dependent8BirthDate>

<Dependent8AccompanyingDependent xsi:type="xsd:string">String</Dependent8AccompanyingDependent>

<Dependent9Relationship xsi:type="xsd:string">String</Dependent9Relationship>

<Dependent9FirstName xsi:type="xsd:string">String</Dependent9FirstName>

<Dependent9MiddleInitial xsi:type="xsd:string">String</Dependent9MiddleInitial>

<Dependent9LastName xsi:type="xsd:string">String</Dependent9LastName>

<Dependent9Gender xsi:type="xsd:string">String</Dependent9Gender>

<Dependent9BirthDate xsi:type="xsd:string">String</Dependent9BirthDate>

<Dependent9AccompanyingDependent xsi:type="xsd:string">String</Dependent9AccompanyingDependent>

<Dependent10Relationship xsi:type="xsd:string">String</Dependent10Relationship>

<Dependent10FirstName xsi:type="xsd:string">String</Dependent10FirstName>

<Dependent10MiddleInitial xsi:type="xsd:string">String</Dependent10MiddleInitial>

<Dependent10LastName xsi:type="xsd:string">String</Dependent10LastName>

<Dependent10Gender xsi:type="xsd:string">String</Dependent10Gender>

<Dependent10BirthDate xsi:type="xsd:string">String</Dependent10BirthDate>

<Dependent10AccompanyingDependent xsi:type="xsd:string">String</Dependent10AccompanyingDependent>

<FutureUse1 xsi:type="xsd:string">String</FutureUse1>

<FutureUse2 xsi:type="xsd:string">String</FutureUse2>

<FutureUse3 xsi:type="xsd:string">String</FutureUse3>

<FutureUse4 xsi:type="xsd:string">String</FutureUse4>

<FutureUse5 xsi:type="xsd:string">String</FutureUse5>

<FutureUse6 xsi:type="xsd:string">String</FutureUse6>

<FutureUse7 xsi:type="xsd:string">String</FutureUse7>

<FutureUse8 xsi:type="xsd:string">String</FutureUse8>

<FutureUse9 xsi:type="xsd:string">String</FutureUse9>

<FutureUse10 xsi:type="xsd:string">String</FutureUse10>

<AuthorizedInitiatorGender xsi:type="xsd:string">String</AuthorizedInitiatorGender>

<AuthorizedInitiatorFirstName xsi:type="xsd:string">String</AuthorizedInitiatorFirstName>

<AuthorizedInitiatorLastName xsi:type="xsd:string">String</AuthorizedInitiatorLastName>

<AuthorizedInitiatorBusinessTelephone xsi:type="xsd:string">String</AuthorizedInitiatorBusinessTelephone>

<AuthorizedInitiatorBusinessEmail xsi:type="xsd:string">String</AuthorizedInitiatorBusinessEmail>

<AuthDate xsi:type="xsd:string">String</AuthDate>

<EmployeeID xsi:type="xsd:string">String</EmployeeID>

<FundingReport xsi:type="xsd:string">String</FundingReport>

<LocationNumber xsi:type="xsd:string">String</LocationNumber>

<PayrollNumber xsi:type="xsd:string">String</PayrollNumber>

<Project xsi:type="xsd:string">String</Project>

<Subjob xsi:type="xsd:string">String</Subjob>

<ClientInternationalFlag xsi:type="xsd:string">String</ClientInternationalFlag>

<RelocationSAPType xsi:type="xsd:string">String</RelocationSAPType>

<RelocationMoveType xsi:type="xsd:string">String</RelocationMoveType>

<RelocationMoveTypeReason xsi:type="xsd:string">String</RelocationMoveTypeReason>

<RelocationAssignType xsi:type="xsd:string">String</RelocationAssignType>

<RelocationAssignStat xsi:type="xsd:string">String</RelocationAssignStat>

<Reloc xsi:type="xsd:string">String</Reloc>

<Ship xsi:type="xsd:string">String</Ship>

<Storage xsi:type="xsd:string">String</Storage>

<Expense xsi:type="xsd:string">String</Expense>

<CompanyCode xsi:type="xsd:string">String</CompanyCode>

<OutOfPolicy xsi:type="xsd:string">String</OutOfPolicy>

<OOPShipMent xsi:type="xsd:string">String</OOPShipMent>

<OOPStorage xsi:type="xsd:string">String</OOPStorage>

<OOPTravel xsi:type="xsd:string">String</OOPTravel>

<CitizenShip xsi:type="xsd:string">String</CitizenShip>

<ResidentAlien xsi:type="xsd:string">String</ResidentAlien>

<NationalToUS xsi:type="xsd:string">String</NationalToUS>

<OOPReloc xsi:type="xsd:string">String</OOPReloc>

<ShipAllowAir xsi:type="xsd:string">String</ShipAllowAir>

<ShipAllowSurface xsi:type="xsd:string">String</ShipAllowSurface>

<ShipAllowNA xsi:type="xsd:string">String</ShipAllowNA>

<StorAllowMaximum xsi:type="xsd:string">String</StorAllowMaximum>

<StorAllowNA xsi:type="xsd:string">String</StorAllowNA>

</m:Authorization>

</SOAP-ENV:Body>

</SOAP-ENV:Envelope>

henrique_pinto
Active Contributor
0 Kudos

A quick way of finding out your web service's right address and soapaction using XML Spy is:

1. Go to Soap, create new soap request

2. enter the full address of your wsdl (it should be link?wsdl or something like that);

3. select the operation you want to access;

4. after the request has been generated, go to Soap, Change Soap request parameters.

And that's it.

The address you should access (meaning, the Target URL you must use on your receiver Soap Adapter) is the "Connection Endpoint". The Soapaction is the soapaction you must enter in the adapter, but not necessarily it's used (if it's blank, just leave the soapaction field in your adapter empty).

Some comments on the dude who managed to correct the problem using ?wsdl on the address field. Actually, that makes no sense at all. The ?wsdl address can be used if your webservice has only one operation and all, but it's always better to use the proper address (the one that XML Spy shows to you). Probably you just had to enter your proxy information into XI, so you didn't have to manually grant access to XI's machine in the firewall rules.

The "invalid content type for SOAP: TEXT/HTML" message probably was due to a "403 forbidden" from your firewall or proxy manager. You can check that if you set the rfc adapter trace to debug mode (on Visual Administrator, Server, Services, Log Configurator) and check the defaulttracelog file (on VA, Server, Services, Log Viewer)

Former Member
0 Kudos

Hi Henrique,

Thanks-a-lot for the help. I tried to test the SOAP request,how can I configure the Proxy details for the soap request in Altova. I am getting "authentication failed" message.

Thanks,

Raj.

henrique_pinto
Active Contributor
0 Kudos

As expected, since XML Spy doesn't have any proxy configuration. I think you won't be able to access the webservice through XML Spy, unless you have a non-proxy Internet connection.

Former Member
0 Kudos

Hi Henrique, Ricardo,

in the XML spy, I tested using the XI Payload in the send soap request to server, its working fine..I am getting the respons, of course it has CDATA tags. But in XI, I still get the same error, "Authentication failed".

In XML spy also , if I include <ns1:clsSubmitAuth.Authorization xmlns:ns1="http://tempuri.org/wsdl/"> element in the soap request along with soap envelope, I get " Authentication Failed", which is the same error in XI too.

Any ideas why is it like that?. Is there anything wrong in the SOAP File?.

Thanks and I appreciate your inputs.

Raj.

Former Member
0 Kudos

Raj,

I have same issue. I was ondering how could you solve this issue. Please let me know.

Thank you,

Balaji

Answers (2)

Answers (2)

moorthy
Active Contributor
0 Kudos

Hi,

Check this thread-

SAP Note No: 856597

Hope this helps,

Regards,

Moorthy

Former Member
0 Kudos

I already read this NOTE.

But I don't what's happening...

I try XML Spy and it works fine.

Thanks,

Sílvio

moorthy
Active Contributor
0 Kudos

Hi,

Did you check this Pdf for the Receiever SOAP Adapter configuration-

https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/40728f7b-0401-0010-d9bc-8c7...

Hope it helps,

Regards,

Moorthy

Former Member
0 Kudos

Silvio

This error is may be because of some xml document mismatach. Go through the url:

---Satish