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

I found the problem:

I have this winform 1.1 project where before I started changing the backend
to a .net 2.0 ws project, I copied the entire winform solution to a new
folder and work on this new solution as a staging solution. While I was
working in this new (copied) solution as the code executed, it would refer
back to the code in the old - original solution. This was starting to
really confuse me because when I stepped through the code, I would not see
the edits I had just made.

So fix it, I removed all the projects from the staging solution and re-added
them back in. This cleaned up all the reference issues.

--
moondaddy@xxxxxxxxxxxxxxx
"Steven Cheng[MSFT]" <stcheng@xxxxxxxxxxxxxxxxxxxx> wrote in message
news:xC%23%23ZnXeGHA.764@xxxxxxxxxxxxxxxxxxxxxxxx
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: app type
    ... The logger may be used in a winform, webform or in a webservice. ... This way your logging component can ...
    (microsoft.public.dotnet.general)
  • Re: Starting exe from WebService
    ... I need to execute the program through the webservice ... WebService because the program is complicated and I don't ... WinForm app is getting ... >Why do you want a WebMethod to launch a WinForm on the ...
    (microsoft.public.dotnet.framework.aspnet.security)
  • Code Access Security Problems in IE-hosted Winform
    ... I have a winform that I host in IE, ... error when I try to access my webservice. ... I then made sure that MyServer is part of my Local Intranet Zone ...
    (microsoft.public.dotnet.framework.aspnet.security)
  • Re: call from a webservice to a windows Form
    ... > something more efficient like remoting or named pipes, ... Because the WinForm isn't the client of the webservice. ...
    (microsoft.public.dotnet.languages.csharp)
Loading