SOAP: error occured: java.io.IOException: invalid content type for SOAP

[Former Member]

hello,,

I’m trying to sending a message via sender soap adapter and I’m receiving this error :

SOAP: error occured: java.io.IOException: invalid content type for SOAP: TEXT/HTML

Exception caught by adapter framework: invalid content type for SOAP: TEXT/HTML

Delivery of the message to the application using connection AFW failed, due to: invalid content type for SOAP: TEXT/HTML.

Please advice..

[Former Member]

I also received this message during testing with a partner.

This message may be given for mutiple reasons, but it was resolved after it was determined that the receiver could not accept the XML file with a SOAP envelope.

I checked the "Do not include envelope" checkbox for the communication channel and the file went though!

Try it!

Thanks,

Jeff Schreiber

[Former Member]

Chaitanya Arora,

Please have a look at the following note:

856597 - FAQ: XI 3.0 SOAP Adapter

[former_member187339]

Hi,

Check these threads:

Regards

Suraj

[moorthy]

Hi,

Verify your SOAP Adapter Configurtaion-

-Target URL should be wsdl URL in your SOAP Adapter

Check this thread-

Regards,

Moorthy

[Former Member]

Hello Krishna...

i checked the target URL.. its fine....

when i access that URL.. its showing the XML code...

Please advice...

[moorthy]

DId you check exactly as mentioned in the given thread?

What is your Target URL..? Given thread had same/similar problem, it has got resolved..

There is a pdf, mentioned by me ,check for the URL format.

<i>when i access that URL.. its showing the XML code...</i>

>>This is Ok..

REgards,

Moorthy

[Former Member]

Hi Chaitanya Arora

How did you resolve this issue.

We are also getting error when we call a web service from XI

SOAP: error occured: com.sap.aii.af.ra.ms.api.RecoverableException: java.io.IOException: invalid content type for SOAP: TEXT/HTML

Exception caught by adapter framework: java.io.IOException: invalid content type for SOAP: TEXT/HTML

Regards

NS Rajagopal

[henrique_pinto]

People,

most of errors like that are 401 (unauthorized), 403 (forbidden), 404 (not found) and so on. To be sure, check the message content that comes back from the webservice, in the Message Monitoring.

Obs: To visualize sync messages payload in Message Monitoring, you'll have to set the Messaging.syncMessageRemover.removebody parameter to <i>false</i> (default is <i>true</i>) in SAP XI AF Messaging service, in the Visual Administrator.

Regards,

Henrique.