Server did not recognize the value of HTTP Header SOAPAction.

[Brian Begy]

Hi everyone,

I'm posting my experience here as a guide to others.

We have a VB.NET desktop app that connects to an ASP.NET web service for
database services. Complex business objects are shared between the
client and server and are serialized with the xml serialization
libraries. We have released something like 35 iterations of the
application so far, and since we frequently change the desktop and web
services at the same time, we have been creating new web services in new
directories, and copying the latest version of the app to our clients
with xcopy. When we do so, we blast the old copy of the app and any
dll's.

For example, version 1.2.1 of the desktop app connects to
http://www.mydomain.com\webservice\1_2_1\webservice.asmx.

We have found that sometimes, a file called applicationname.exe.config
contains a reference to an old version of the web service, say,
http://www.mydomain.com\webservice\1_0_3\webservice.asmx. This
incompatibility causes the server to reject our calls to web services
(before any server side error handling code can be invoked) with the
cryptic error message: Server did not recognize the value of HTTP Header
SOAPAction.

Blasting the applicationname.exe.config file solves the problem. Since
this is not documented anywhere as near as I can tell, I wanted to post
it here before this problem drives anyone else crazy. I spent all
morning google-ing for references to this problem and couldn't find any.

Cheers all.

Brian

Brian Begy
Developer
Chicago Data Solutions
www.chicagodatasolutions.com
br...@chicagodatasolutions.com

*** Sent via Developersdex http://www.developersdex.com ***
Don't just participate in USENET...get rewarded for it!