SOAP Communication channel monitioring error.

[Former Member]

Hi guru's

Message processing failed. Cause: com.sap.aii.af.ra.ms.api.RecoverableException: invalid content type for SOAP: TEXT/HTML; HTTP 403 Forbidden: java.io.IOException: invalid content type for SOAP: TEXT/HTML; HTTP 403 Forbidden

SOAP: call failed: java.io.IOException: invalid content type for SOAP: TEXT/HTML; HTTP 403 Forbidden

I am checked what the other members have said, but still i am getting the same error. any inputs please.

Thanks.

[Former Member]

there was issue with the certificates which got expired. Whenever you install new certificates just activate the integration directory and restart the comm.channels

[Shabarish_Nair]

/people/shabarish.vijayakumar/blog/2008/01/08/troubleshooting--rfc-and-soap-scenarios-updated-on-20042009

do try taking the help of the blog to help you troubleshoot.

If you confirm your adapter configuration is fine, then try to check if there is a proxy server in your network and if you have configured the same in your CC

[Former Member]

Hi Latha,

403 meaning is given here: http://www.checkupdown.com/status/E403.html

So either your paylaod what ever you are sending is wrong. So send it from altova xml spy and from your original webservice. Then compare both of your payloads, You should see the difference somewhere.

Regards,

---Satish

[Former Member]

where are u trying to trigger the webservice from?

before triggering it from any application, maybe use altova or something and try to trigger ur wsdl.

[former_member187339]

Hi,

Can you detailed your scenario. It seems the user (given in channel) which calls the webservice is not having enough authorizations to exute the wsdl.

Regards

Suraj

[former_member200962]

Confirm the following:

1) USer-id and Password used in the SOAP CC are accurate

2) No error in the Target URL mentioned in the SOAP CC.....any space/ unwanted character....should be exactly same as in the WSDL file that you have imported in IR

Regards,

Abhishek.