This error occurs usually when the client/server bindings mismatches, wherein the message version in the service uses SOAP 1.2 i.e WSHttpBinding which expects application/soap+xml and the version in the client uses SOAP 1.1 i.e. BasicHttpBinding which sends text/xml or vice-verse.
Check with the interface, you might need to ask interface to change code of the web service to reflect the right binding.
Thanks Manoj for Reply.
Is there any way we can find out what is the required binding for Remedy. As per integration guide Soap1.2 is supported while consuming web services.
Do we have any config file setting in Remedy to look for/change parameters for consuming web service. I have checked pluginsvr_config file.
Hi Manesh Laddha,
We have the same problem...did you solve it?