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

[former_member245887]

Hi,

I have this error on a SOAP Receiver Channel: invalid content type for SOAP: TEXT/HTML; HTTP 500 Internal Server Error

I've found several threads on SDN Forums about similar errors, but I did not find a solution for my problem yet.

I checked this blog: /people/shabarish.vijayakumar/blog/2008/01/08/troubleshooting--rfc-and-soap-scenarios-updated-on-20042009 Pt.6 applies to my situation, but the proposed solution doesn't solve the problem.

TRACE Messaging System

u2026

2011-06-06 10:59:41.822 Success Delivering to channel: CC_SOAP_RCV_XXX

2011-06-06 10:59:41.823 Success MP: entering1

2011-06-06 10:59:41.825 Success MP: processing local module localejbs/sap.com/com.sap.aii.af.soapadapter/XISOAPAdapterBean

2011-06-06 10:59:41.828 Success SOAP: request message entering the adapter with user J2EE_GUEST

2011-06-06 10:59:42.012 Error SOAP: call failed: java.io.IOException: invalid content type for SOAP: TEXT/HTML; HTTP 500 Internal Server Error

2011-06-06 10:59:42.014 Success SOAP: sending a delivery error ack ...

2011-06-06 10:59:42.014 Success SOAP: sent a delivery error ack

u2026

Message Details

Address http://aaa.bbb.be:54000/MessagingSystem/receive/AFW/XI

Credential PasswordCredential(PIISUSER):password=********

Transport Headers accept-encoding=gzip sap-xi-messageid=4DEA11FE90003094E10000000AE908B4 content-length=7520 http=POST host= aaa.bbb.be:54000 user-agent=SAP NetWeaver Application Server (1.0;711) content-type=multipart/related;boundary=SAP_4DEA47CEAD3A5138E10000000AE908B4_END;type="text/xml";start="" soapaction="http://sap.com/xi/XI/Message/30"

Configuration Details SOAP Communication Channel

SOAP Receiver Channel

No modules configured

Do not use SOAP Envelope -> NOT checked

If I type the target URL in browser it opens (no login required) and I see the available web services.

Anyone any idea what's the reason for this error?

Thanks in advance

Kind Regards

Edmond Paulussen

[Former Member · Accepted solution]

Hi Edmond,

This Error is usually caused due to data(payload) problem (blank fields, too long string, etc...)

Try checking the data, and try putting the message in message mapping to check it.

[former_member245887 · Accepted solution]

Hi, Zevik,

Thank you for your reply. I think you are right, but the problem is how to detect what and where it went wrong.

When in PI Messaging System I try to display the message bytes, I get a Shakespearian reply: "Hitherto shalt thou come, but no further"

The message is formd by SAP PI: message mapping and then SOAP Adapter, so I would think it is formed according to the standards. When I look at the message details, all looks OK.

Maybe it's a processing problem at the 3rd party that receives the messages.

Kind Regards

Edmond

[Former Member · Accepted solution]

Hi Edmond,

the key to knowing what is wrong with the payload is checking it in message mapping, if you have done that and it is Ok, so probably the problem is in the target system, you should use SOAPUI to be sure.

Have a good day,

Zevik

[Former Member]

This problem can be caused by the PI can not access the URL of the web service.

In the PI server run the command ping and telnet.

ping <url.web.service>

Take the IP return and run the telnet command.

telnet <IP> <PORT>

The connection to the web service has to close.

If the connection does not close, release the firewall server's PI to the IP of the web service.

[Former Member]

Hi, Marlon Sperandio Monteiro!

I have this problem too.

I see the web service in browser and telnet connects to service, but connection do not close automatically. Where have I "release the firewall server's PI to the IP of the web service"?.

I don't understand. If server firewal port between the PI and web service not open telnet would not connected and browser nothing would show.

[markangelo_dihiansan]

Hello,

If I type the target URL in browser it opens (no login required) and I see the available web services.

It is possible that the URL that you are connecting to only lists the available web services but not necessarily invoke them. Can you try using a third party tool such as fiddler to see the actual HTTP request going to the URL? By the way, have you filled out the soap action?

Hope this helps,

Mark

Edited by: Mark Dihiansan on Jun 7, 2011 3:48 AM

[Former Member]

Hi Edmond,

We faced similar problem & found alternative.

Try out, if it works for u as well.

1) Use HTTP Adapter instead of SOAP.

Transport Protocol : HTTP 1.0

Message Protocol : XI Payload in HTTP Body

Adapter Engine : Integration Server

Addressing type : URL Address.

Target Host:

Service Number :

Path Prefix:

Authentication type : we hv used Ananymus login, as our login details in payload header.

Content Type : application/soap+xml;charset=UTF-8( this is IMP).

Header Fields.

Name value

Host target host

XI Payload Manipulation

XML Code : UTF-8

Hope, this helps...

-santosh.

[former_member245887]

Hi,

Thank you for the reply.

I also need to supply a soap action. Is that possible with the http adapter?

Where should I specify it?

Kind Regards

Edmond

[markangelo_dihiansan]

Hello,

I also need to supply a soap action. Is that possible with the http adapter?
Where should I specify it?

No, not possible. If the webservice has a specification for a pure HTTP POST, you can use that. No need to specify a soap action.

Hope this helps,

Mark

[former_member245887]

Hi Mark,

How can I find out if this is the case?

Edmond

[former_member245887]

Hi Santosh,

I tried your suggestion. Still get the HTTP 500 error. This must be a problem at the 3rd party that receives our messages.

Kind Regards

Edmond

[Former Member]

Try testing the WSDL in SOAPUI to ensure third party setup is working fine...

-santosh.

[baskar_gopalakrishnan2]

Just few cents ...

a) The problem might be target URL you specified in the SOAP receiver communication channel.

>If I type the target URL in browser it opens (no login required) and I see the available web services.

Try to specify in url field of channel without ?wsdl

Example: If your browser URL is http:// xxxx/ws/service?wsdl,

then specify in soap receiver as http://xxxx/ws/service

b) Check with XMLSPY or SOAPUI and test the WSDL without PI first and make sure what is the right URL to point out....