RE: Server did not recognize the value of HTTP Header SOAPAction

Hi Moondady,

Welcome to the ASPNET newsgroup.

From your description, I understand you've developed an ASP.NET webservice
which is consumed by a winform client application. Both ones are
constructed under .net framework 1.1. Recently, you upgrade the webservice
from ASP.NET 1.1 to ASP.NET 2.0, after that the 1.1 winform client broke
and reported the "Server did not recognize the value of HTTP Header
SOAPAction" error ,correct?

Based on my experience, since http SoapAction headeris used to identify the
webmethod of a certain webservice, the problem is likely due to the client
application is sending an unexpected SoapAction header to the service. And
in ASP.NET webservice, the SoapAction header will be determined by both the
service's namespace and the Action property set on the WebMethod attribute.


#WebServiceAttribute.Namespace Property
http://msdn2.microsoft.com/en-us/library/system.web.services.webserviceattri
bute.namespace(VS.80).aspx

#SoapDocumentMethodAttribute.Action Property
http://msdn2.microsoft.com/en-us/library/system.web.services.protocols.soapd
ocumentmethodattribute.action.aspx

Have you explicitly set this property for your webservice and the
webmethod? Also, for general troubleshooting, you can create a .net 2.0
webservice proxy to see whether it can work correctly. If it works, you can
compare the 2.0 client's generated proxy code with 1.1 client's code or you
can use some trace tools to capture the raw SOAP xml message sent by
different clients to find the difference between them.

Hope this helps.

Regards,

Steven Cheng
Microsoft Online Community Support


==================================================

When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.

==================================================


This posting is provided "AS IS" with no warranties, and confers no rights.



Get Secure! www.microsoft.com/security
(This posting is provided "AS IS", with no warranties, and confers no
rights.)




.

Relevant Pages

  • Re: WSE352 Size of the record exceed its limit
    ... The webservice is a WSE service component soap client. ... you're developing an .net webservice which uses WSE ...
    (microsoft.public.dotnet.framework.webservices)
  • RE: Error on SOAP Call on only one machine: Could not find default endpoint element that references
    ... "Service Reference" is a proxy class used for consuming WCF service. ... Though WCF client can also consume standard XML webservice, ... Microsoft MSDN Online Support Lead ...
    (microsoft.public.dotnet.languages.vb)
  • Re: Webservice problem (after iisreset)
    ... I was speaking about whatever means you're suing the make the call from the client. ... If it already waits one minute for the failure then it sounds like the timeout is already high enough. ... So use wsdl.exe to generate a .NET proxy to your webservice to see if that style of client has the same problems or not. ... If it does, then it sounds like something on the server, if it does not then it's likley your HTC framework. ...
    (microsoft.public.dotnet.framework.aspnet.webservices)
  • Re: How does the client of a webservice figure out a complex type
    ... attribute with a hint for the client side proxy this is a DataSet. ... >if the wsdl does not contain any reference, ... >> As for how webservice client figure out a complex type, ...
    (microsoft.public.dotnet.framework.webservices)
  • asynchrone Webmethode
    ... Dieser Webservice empfängt vom Client (WinForm-Applikation) ... Diese Anfrage und die zugehörige Datei soll in eine Queue gestellt ... Webservice die Resultat-Binärdatei abholen. ...
    (microsoft.public.de.german.entwickler.dotnet.csharp)