Invalid content type for SOAP: TEXT/HTML; HTTP 500 Internal Server Error

[Former Member]

Hello! All

We have a a synchronous AAE scenario SOAP to ABAP Proxy (using SOAP Adapter).

when testing this interface, by sending request from SOAP UI, the sender SOAP communication channel is throwing the following error:

**************************************************************

com.sap.engine.interfaces.messaging.api.exception.MessagingException: com.sap.engine.interfaces.messaging.api.exception.MessagingException: java.io.IOException: invalid content type for SOAP: TEXT/HTML; HTTP 500 Internal Server Error

**************************************************************

The URL and payload seem to be good, not sure what is causing the issue.

Can you please let us know if anyone came across similar issue and what the possible issue/resolution could be.

Your help is greatly appreciated!!

Thank you,

Ritu

[VijayKonam · Accepted solution]

Check if the service definition changed and whether the XML instance is in sync with the service expectation.

VJ

[Former Member · Accepted solution]

Hello! All

Thank you for your response ... apologies for the late update on this ...

The issue was with the ABAP proxy class - this was working fine in DEC. However the ABAP Proxy did not get transported to the ECC QA environment correctly - was missing something in the prxoy class. Re- transporting the ECC object fixed the issue.

Thank you,

Ritu

[Former Member]

Hi Ritu,

Problem is with Server/SOAP adapter servlet where you are posting the data through SOAP UI and not the SOAP data. Here Server means PI Server where SOAP adapter is running and SOAP adapter has the Message Servlet to which you are POSTing the data through SOAP UI.

So take out the SOAP sender adapter url and provide same thing in the Internet Explorere or any web broser and try to open it. If it's giving same problem as 500 Internal error then you should check the host and port and url name. This would confirm whether url is correct or not.

Thanks,

RK

[iaki_vila]

If your SOAP message has a caracter like ñ, á, é, etc you might put an XML header like <?xml version="1.0" encoding="UTF-8"?>.

You could try also with the SOAP parameters, for example don't mark the option "Keep Attachments", etc

Regards