Server did not recognize the value of HTTP Header SOAPAction

Question

SoapRpcMethod Action    http   cyberindigo TempWebService InsertXML       RequestNamespace    http   cyberindigo TempWebService Request       RequestElementName    InsertXMLRequest       ResponseNamespace    http   cyberindigo TempWebService Response       ResponseElementName    InsertXMLResponse       Use   System Web Services Description SoapBindingUse Literal         WebMethod      public string InsertXML string Jobs                return  Hi           The Problem when I am accessing it using XMLHttpRequest it gives following error  Server did not recognize the value of HTTP Header SOAPAction  http   Cyberindigo TempWebService InsertXML

User · Answer

I ve decided to post my own answer here because I ve lost a few hours on this and I think that  although the accepted answer is very good and pointed me in the right direction  yes  it got a voteup   it was not detailed enough to explain what was wrong with my application  at least in my case   I m running a BPEL module in OpenESB 2 2 and the Test Case of my Composite Application was failing with the following error   Caused by  System Web Services Protocols SoapException  Server did not recognize the value of HTTP Header SOAPAction      After doing some research I ve noticed that the external WSDL has all the clues we need to fix this problem  e g   I m using the following web service to validate a credit card number through a orchestration of Web Services  http   www webservicex net CreditCard asmx WSDL  If you check the  lt wsdl operation elements you will see that it clearly states the soapAction for that operation    lt wsdl binding name  CCCheckerSoap  type  tns CCCheckerSoap  gt     lt soap binding transport  http   schemas xmlsoap org soap http   gt     lt wsdl operation name  ValidateCardNumber  gt       lt soap operation soapAction  http   www webservicex net ValidateCardNumber  style  document   gt       lt wsdl input gt     lt soap body use  literal   gt   lt  wsdl input gt        But  once you create the Composite Application and build the project with the BPEL that invokes this external WSDL service  for some reason  bug    the XML of the Composite Application Service Assembly  CASA  binding is generated with an empty soapAction parameter    lt binding name  casaBinding1  type  ns CCCheckerSoap  gt           lt soap binding style  document  transport  http   schemas xmlsoap org soap http   gt           lt operation name  ValidateCardNumber  gt               lt soap operation soapAction    style  document   gt               lt input gt                   lt soap body use  literal   gt               lt  input gt    Once you copy the proper soapAction  http   www webservicex net ValidateCardNumber  into this parameter  the application s Test Case will correctly and return the expected Soap response    lt soap operation soapAction  http   www webservicex net ValidateCardNumber  style  document   gt    So  it s a more specific solution that I decided to document based on the information found in this blog post  http   bluebones net 2003 07 server-did-not-recognize-http-header-soapaction       It means  at least in my case  that you are accessing a web service   with SOAP and passing a SOAPAction parameter in the HTTP request   that does not match what the service is expecting

User · Answer

I had same problem  it fixed after some checking    lt  lt  Target WebService Exists but called method s not eXXXists         my local service contain methods but target server connecting server    does not contain specified called method    Check your program scenario again

User · Answer

The source of the next part of this post is       http   bluebones net 2003 07 server-did-not-recognize-http-header-soapaction      since the OP didn t want to give attribution  and thanks to Peter   Please note that bakert is the original author of the text  not the OP     Seeing as nowhere on the internet can I find an explanation of this error I thought I   d share the fruits of my long search for this bug   It means  at least in my case  that you are accessing a web service with SOAP and passing a SOAPAction parameter in the HTTP request that does not match what the service is expecting   I got in a pickle because we moved a web service from one server to another and thus I changed the    namespace     don   t get confused between web service namespaces and  net namespaces  in the calling C  file to match the new server  But the server doesn   t care about the actual web reality of http   yournamespace com blah it only cares that you send it what you have said you are expecting on the server  It doesn   t care if there   s actually anything there or not   So basically the web service was moved from http   foo com servicename to http   bar com servicename but the    namespace    of the web service stayed as http   foo com servicename because no one changed it   And that only took about 4 hours to work out   If you   re having a similar problem but can   t work what I   m saying here  feel free to mail me on bakert web gmail com     I wouldn   t wish my four hours on anyone

User · Answer

I had a similar problem with the same error message   System Web Services Protocols SoapException  Server did not recognize the value of HTTP Header SOAPAction   We utilize dynamic URL s in our web service calls   We have a central configuration server that manages the location of all web service calls so that our code can run in DEV  test or live without recompiling   The URL for a specific web service call for the test environment was incorrect in our configuration server   The web service call was being sent to the wrong server and the wrong web service     So this error can simply be the result of the web service request not matching the web service being called    It took running fiddler on the Web App server to see that the actual call was to the incorrect web service

User · Answer

Just to help someone on this problem  after an afternoon of debug  the problem was that the web service was developed with framework 4 5 and the call from android must be done with SoapEnvelope VER12 and not with SoapEnvelope VER11

User · Answer

We had renamed some of our webservice project namespaces and forgot to update the website httphandlers config section with the namespace of the renamed projects

User · Answer

the problem is in the System Web Services Protocols SoapDocumentMethodAttribute in the service  Please check it  it may changed

User · Answer

I had this same problem  but the solution for me was that I was pointing to the wrong web service  I had updated the web reference correctly  But we store the URl for the service in an encrypted file  and I didn t update the file with the correct service encrypted   But all these suggestions really helped me to realize where to go for debugging   Thanks

User · Answer

I had the same error  i was able to resolve it by removing the  Web Reference  and adding a  Service Reference  instead

User · Answer

I had this same problem  but the solution for me was that I was pointing to the wrong web service  I had updated the web reference correctly  But we store the URl for the service in an encrypted file  and I didn t update the file with the correct service encrypted   But all these suggestions really helped me to realize where to go for debugging   Thanks

User · Answer

While calling the  asmx   wcf web service please take care of below points    The namespace is case sensitive the SOAP request MUST be sent with the same namespace with which the WebService is declared     e g  For the WebService declared as below   WebService Namespace    http   MyDomain com TestService     public class FooClass   System Web Services WebService        WebMethod         public bool Foo  string name                                         The SOAP request must maintain the same case for namespace while calling Sometime we overlook the case sensitivity       lt soap Envelope xmlns xsi  http   www w3 org 2001 XMLSchema-instance  xmlns xsd  http   www w3 org 2001 XMLSchema  xmlns soap  http   schemas xmlsoap org soap envelope   gt     lt soap Body gt        lt Foo xmlns  http   MyDomain com TestService  gt        lt name gt string lt  name gt              lt  Foo gt     lt  soap Body gt    lt  soap Envelope gt     The namespace need not be same as hosted url of the service The namespace can be any string    e g  Above service may be hosted at http   84 23 9 65 MyTestService   but still while invoking the Web Service from client the namespace should be the same which the serice class is having i e http   MyDomain com TestService

User · Answer

We had renamed some of our webservice project namespaces and forgot to update the website httphandlers config section with the namespace of the renamed projects

User · Answer

I got this error when I tried to call a method which did not exist  It only existed in a newer version of our webservice

User · Answer

My error fixed by answer Mr  John Saunders   http   forums asp net post 2906487 aspx  in short  difference between Namespace of ws  asmx cs with ws  wsdl files   1   WebService Namespace    http   tempuri org       later web service namespace changed to    2   WebService Namespace    http   newvalue com       so we referenced  1  in application and web service is  2  now   make them equal to fix your problem

User · Answer

I had same problem  it fixed after some checking    lt  lt  Target WebService Exists but called method s not eXXXists         my local service contain methods but target server connecting server    does not contain specified called method    Check your program scenario again

User · Answer

Just to help someone on this problem  after an afternoon of debug  the problem was that the web service was developed with framework 4 5 and the call from android must be done with SoapEnvelope VER12 and not with SoapEnvelope VER11

User · Answer

While calling the  asmx   wcf web service please take care of below points    The namespace is case sensitive the SOAP request MUST be sent with the same namespace with which the WebService is declared     e g  For the WebService declared as below   WebService Namespace    http   MyDomain com TestService     public class FooClass   System Web Services WebService        WebMethod         public bool Foo  string name                                         The SOAP request must maintain the same case for namespace while calling Sometime we overlook the case sensitivity       lt soap Envelope xmlns xsi  http   www w3 org 2001 XMLSchema-instance  xmlns xsd  http   www w3 org 2001 XMLSchema  xmlns soap  http   schemas xmlsoap org soap envelope   gt     lt soap Body gt        lt Foo xmlns  http   MyDomain com TestService  gt        lt name gt string lt  name gt              lt  Foo gt     lt  soap Body gt    lt  soap Envelope gt     The namespace need not be same as hosted url of the service The namespace can be any string    e g  Above service may be hosted at http   84 23 9 65 MyTestService   but still while invoking the Web Service from client the namespace should be the same which the serice class is having i e http   MyDomain com TestService

User · Answer

I had a similar problem with the same error message   System Web Services Protocols SoapException  Server did not recognize the value of HTTP Header SOAPAction   We utilize dynamic URL s in our web service calls   We have a central configuration server that manages the location of all web service calls so that our code can run in DEV  test or live without recompiling   The URL for a specific web service call for the test environment was incorrect in our configuration server   The web service call was being sent to the wrong server and the wrong web service     So this error can simply be the result of the web service request not matching the web service being called    It took running fiddler on the Web App server to see that the actual call was to the incorrect web service

User · Answer

I found out that my web reference was out of date and the code was calling a removed web service

User · Answer

the problem is in the System Web Services Protocols SoapDocumentMethodAttribute in the service  Please check it  it may changed

User · Answer

I had similar issue  To debug the problem  I ve run Wireshark and capture request generated by my code  Then I used XML Spy trial to create a SOAP request  assuming you have WSDL  and compared those two   This should give you a hint what goes wrong

User · Answer

I had to sort out capitalisation of my service reference  delete the references and re add them to fix this  I am not sure if any of these steps are superstitious  but the problem went away

User · Answer

I found out that my web reference was out of date and the code was calling a removed web service

User · Answer

I had similar issue  To debug the problem  I ve run Wireshark and capture request generated by my code  Then I used XML Spy trial to create a SOAP request  assuming you have WSDL  and compared those two   This should give you a hint what goes wrong

User · Answer

I had the same problem after changing the namespace from  tempuri  in my Web Service   You have to update your Service Reference in the project that is consuming the above service  so it can get the latest SOAP definitions   Or at least that worked for me

User · Answer

I agree with Sam in that the SOAP definition does not match what is expected  Here is just ONE solution it could be  I had to manually figure this error for myself   My problem was that I changed the name of the web method but did not change the  MessageName  in the metadata tag    WebMethod MessageName    foo    public string bar          It should be   WebMethod MessageName    foo    public string foo          hope that helps someone

User · Answer

The source of the next part of this post is       http   bluebones net 2003 07 server-did-not-recognize-http-header-soapaction      since the OP didn t want to give attribution  and thanks to Peter   Please note that bakert is the original author of the text  not the OP     Seeing as nowhere on the internet can I find an explanation of this error I thought I   d share the fruits of my long search for this bug   It means  at least in my case  that you are accessing a web service with SOAP and passing a SOAPAction parameter in the HTTP request that does not match what the service is expecting   I got in a pickle because we moved a web service from one server to another and thus I changed the    namespace     don   t get confused between web service namespaces and  net namespaces  in the calling C  file to match the new server  But the server doesn   t care about the actual web reality of http   yournamespace com blah it only cares that you send it what you have said you are expecting on the server  It doesn   t care if there   s actually anything there or not   So basically the web service was moved from http   foo com servicename to http   bar com servicename but the    namespace    of the web service stayed as http   foo com servicename because no one changed it   And that only took about 4 hours to work out   If you   re having a similar problem but can   t work what I   m saying here  feel free to mail me on bakert web gmail com     I wouldn   t wish my four hours on anyone

User · Answer

I had the same error  i was able to resolve it by removing the  Web Reference  and adding a  Service Reference  instead

User · Answer

I had to sort out capitalisation of my service reference  delete the references and re add them to fix this  I am not sure if any of these steps are superstitious  but the problem went away

User · Answer

I ve decided to post my own answer here because I ve lost a few hours on this and I think that  although the accepted answer is very good and pointed me in the right direction  yes  it got a voteup   it was not detailed enough to explain what was wrong with my application  at least in my case   I m running a BPEL module in OpenESB 2 2 and the Test Case of my Composite Application was failing with the following error   Caused by  System Web Services Protocols SoapException  Server did not recognize the value of HTTP Header SOAPAction      After doing some research I ve noticed that the external WSDL has all the clues we need to fix this problem  e g   I m using the following web service to validate a credit card number through a orchestration of Web Services  http   www webservicex net CreditCard asmx WSDL  If you check the  lt wsdl operation elements you will see that it clearly states the soapAction for that operation    lt wsdl binding name  CCCheckerSoap  type  tns CCCheckerSoap  gt     lt soap binding transport  http   schemas xmlsoap org soap http   gt     lt wsdl operation name  ValidateCardNumber  gt       lt soap operation soapAction  http   www webservicex net ValidateCardNumber  style  document   gt       lt wsdl input gt     lt soap body use  literal   gt   lt  wsdl input gt        But  once you create the Composite Application and build the project with the BPEL that invokes this external WSDL service  for some reason  bug    the XML of the Composite Application Service Assembly  CASA  binding is generated with an empty soapAction parameter    lt binding name  casaBinding1  type  ns CCCheckerSoap  gt           lt soap binding style  document  transport  http   schemas xmlsoap org soap http   gt           lt operation name  ValidateCardNumber  gt               lt soap operation soapAction    style  document   gt               lt input gt                   lt soap body use  literal   gt               lt  input gt    Once you copy the proper soapAction  http   www webservicex net ValidateCardNumber  into this parameter  the application s Test Case will correctly and return the expected Soap response    lt soap operation soapAction  http   www webservicex net ValidateCardNumber  style  document   gt    So  it s a more specific solution that I decided to document based on the information found in this blog post  http   bluebones net 2003 07 server-did-not-recognize-http-header-soapaction       It means  at least in my case  that you are accessing a web service   with SOAP and passing a SOAPAction parameter in the HTTP request   that does not match what the service is expecting

User · Answer

I got this error when I tried to call a method which did not exist  It only existed in a newer version of our webservice

User · Answer

I had the same problem after changing the namespace from  tempuri  in my Web Service   You have to update your Service Reference in the project that is consuming the above service  so it can get the latest SOAP definitions   Or at least that worked for me

User · Answer

I had similar issue  To debug the problem  I ve run Wireshark and capture request generated by my code  Then I used XML Spy trial to create a SOAP request  assuming you have WSDL  and compared those two   This should give you a hint what goes wrong

User · Answer

I had similar issue  To debug the problem  I ve run Wireshark and capture request generated by my code  Then I used XML Spy trial to create a SOAP request  assuming you have WSDL  and compared those two   This should give you a hint what goes wrong

User · Answer

I agree with Sam in that the SOAP definition does not match what is expected  Here is just ONE solution it could be  I had to manually figure this error for myself   My problem was that I changed the name of the web method but did not change the  MessageName  in the metadata tag    WebMethod MessageName    foo    public string bar          It should be   WebMethod MessageName    foo    public string foo          hope that helps someone

User · Answer

My error fixed by answer Mr  John Saunders   http   forums asp net post 2906487 aspx  in short  difference between Namespace of ws  asmx cs with ws  wsdl files   1   WebService Namespace    http   tempuri org       later web service namespace changed to    2   WebService Namespace    http   newvalue com       so we referenced  1  in application and web service is  2  now   make them equal to fix your problem

[c#] Server did not recognize the value of HTTP Header SOAPAction

Examples related to c#

Examples related to javascript

Examples related to web-services