Getting "WSE003: The input was not a valid SOAP message" on every call to an WSE 2.0 SoapHttpRouter

858 Views Asked by At

I already tried some different SOAP-messages, even one which has an empty header and body, but without success to get into my SoapHttpRouter-derived class :-(

Also, when I hit the .asmx-URL with the browser it comes to that error.. here detailed stack trace of the error:

[NotSupportedException: WSE003: The input was not a valid SOAP message.]
Microsoft.Web.Services2.Messaging.SoapHttpRouter.System.Web.IHttpAsyncHandler.BeginProcessRequest(HttpContext httpContext, AsyncCallback callback, Object asyncState) +134
   System.Web.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() +8677954
   System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) +155

I hope that someone is out there who had the same problem. I would appreciate your help very much!

3

There are 3 best solutions below

0
On

I recently ran into this issue. The solution for me was to add the SOAPAction HttpHeader to the request, so that the request header looked something like this:

POST <web service url> HTTP/1.1
Content-Type: text/xml; charset=utf-8
SOAPAction: <action url>
Host: <host>
Content-Length: xxx
0
On

Typically when I get that message it's because there is a server side error and it's sending the default HTML error page back instead of the properly formatted SOAP message.

I would try stepping through the server-side code (if possible) to make sure there aren't any problems.

9
On

Were you aware that WSE 2.0 is extremely obsolete? Even more so than WSE 3.0.