Velocity Reviews - Computer Hardware Reviews

Velocity Reviews > Newsgroups > Programming > ASP .Net > Server did not recognize the value of HTTP Header SOAPAction

Reply
Thread Tools

Server did not recognize the value of HTTP Header SOAPAction

 
 
=?Utf-8?B?TWlndWVsIElzaWRvcm8=?=
Guest
Posts: n/a
 
      05-25-2007
Hi,

I've built an ASP.NET 1.1 web service and an ASP.NET 1.1 application that
calls it
is throwing the following exception:

System.Web.Services.Protocols.SoapException: Server did not recognize the
value of HTTP Header SOAPAction: http://ipm.sitefactory.com/Authenticate. at
System.Web.Services.Protocols.Soap11ServerProtocol Helper.RouteRequest() at
System.Web.Services.Protocols.SoapServerProtocol.I nitialize() at
System.Web.Services.Protocols.ServerProtocolFactor y.Create(Type type,
HttpContext context, HttpRequest request, HttpResponse response, Boolean&
abortProcessing)

The web service class definition is:

[WebService(Namespace="http://ipm.sitefactory.com/")]
public class UserService : WebService
{
...
}

The web method definition is:


[WebMethod(Description="Web method description.")]
public User Authenticate(User user)
{
//code
}

I've checked the WSDL and the beginning is as follows:

<wsdl:definitions xmlns:http="http://schemas.xmlsoap.org/wsdl/http/"
xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
xmlns:s="http://www.w3.org/2001/XMLSchema"
xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"
xmlns:tns="http://ipm.sitefactory.com/"
xmlns:tm="http://microsoft.com/wsdl/mime/textMatching/"
xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/"
targetNamespace="http://ipm.sitefactory.com/"
xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/">

The reference to the web method in WSDL is:

<s:element name="Authenticate">
<s:complexType>
<s:sequence>
<s:element minOccurs="0" maxOccurs="1" name="user" type="tns:User" />
</s:sequence>
</s:complexType>
</s:element>

Like you see, the namespace http://ipm.sitefactory.com/ is present
everywhere correctly and I can't understand why the request is not being
routed to the right web method. Everything seems to be correct from the class
definition to the WSDL. Any suggestions?

Thanks in advance,
Miguel Isidoro
 
Reply With Quote
 
 
 
 
John Saunders [MVP]
Guest
Posts: n/a
 
      05-25-2007
"Miguel Isidoro" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> Hi,
>
> I've built an ASP.NET 1.1 web service and an ASP.NET 1.1 application that
> calls it
> is throwing the following exception:
>
> System.Web.Services.Protocols.SoapException: Server did not recognize the
> value of HTTP Header SOAPAction: http://ipm.sitefactory.com/Authenticate.
> at
> System.Web.Services.Protocols.Soap11ServerProtocol Helper.RouteRequest() at
> System.Web.Services.Protocols.SoapServerProtocol.I nitialize() at
> System.Web.Services.Protocols.ServerProtocolFactor y.Create(Type type,
> HttpContext context, HttpRequest request, HttpResponse response, Boolean&
> abortProcessing)
>

....

> The reference to the web method in WSDL is:
>
> <s:element name="Authenticate">
> <s:complexType>
> <s:sequence>
> <s:element minOccurs="0" maxOccurs="1" name="user" type="tns:User" />
> </s:sequence>
> </s:complexType>
> </s:element>


That is not a reference to the webmethod. It is the definition of an XML
element. Perhaps this XML element is intended to be sent to the server, and
perhaps even to the Authenticate method, but the above XML does not define
the Authenticate method (operation in WSDL terminology), and doesn't say
that this element is part of the message handled by the operation.

Look at the rest of your WSDL, in the <wsdl:binding/> and <wsdlortType/>
sections.
--
John Saunders [MVP]


 
Reply With Quote
 
 
 
 
=?Utf-8?B?TWlndWVsIElzaWRvcm8=?=
Guest
Posts: n/a
 
      05-25-2007
Maybe the termonology is incorrect. I have the web service working at my
development machine and in other web servers. However in this one, not. I
compared the WSDL generated in the development machine and in the erroneous
web server and they are exactly the same. I even analysed the client proxy
class and the namespace I defined is correct. So the info that is being
passed by the client is the one expected by the server. I don't have the WSDL
now so I won't be able to check it until monday but with all that I described
before can you figure out a reason for this behavior?

Thanks
Miguel

"John Saunders [MVP]" wrote:

> "Miguel Isidoro" <(E-Mail Removed)> wrote in message
> news:(E-Mail Removed)...
> > Hi,
> >
> > I've built an ASP.NET 1.1 web service and an ASP.NET 1.1 application that
> > calls it
> > is throwing the following exception:
> >
> > System.Web.Services.Protocols.SoapException: Server did not recognize the
> > value of HTTP Header SOAPAction: http://ipm.sitefactory.com/Authenticate.
> > at
> > System.Web.Services.Protocols.Soap11ServerProtocol Helper.RouteRequest() at
> > System.Web.Services.Protocols.SoapServerProtocol.I nitialize() at
> > System.Web.Services.Protocols.ServerProtocolFactor y.Create(Type type,
> > HttpContext context, HttpRequest request, HttpResponse response, Boolean&
> > abortProcessing)
> >

> ....
>
> > The reference to the web method in WSDL is:
> >
> > <s:element name="Authenticate">
> > <s:complexType>
> > <s:sequence>
> > <s:element minOccurs="0" maxOccurs="1" name="user" type="tns:User" />
> > </s:sequence>
> > </s:complexType>
> > </s:element>

>
> That is not a reference to the webmethod. It is the definition of an XML
> element. Perhaps this XML element is intended to be sent to the server, and
> perhaps even to the Authenticate method, but the above XML does not define
> the Authenticate method (operation in WSDL terminology), and doesn't say
> that this element is part of the message handled by the operation.
>
> Look at the rest of your WSDL, in the <wsdl:binding/> and <wsdlortType/>
> sections.
> --
> John Saunders [MVP]
>
>
>

 
Reply With Quote
 
 
 
Reply

Thread Tools

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
random "Server did not recognize the value of HTTP Header SOAPAction" Paul Turelinckx ASP .Net Web Services 0 02-09-2004 12:26 PM
.Net service to .Net client : Server did not recognize the value of HTTP Header SOAPAction: . Matt Greer ASP .Net Web Services 2 02-06-2004 11:26 AM
Adding a new web method gets me the "Server did not recognize the value of HTTP Header SOAPAction" error Steve Evans ASP .Net Web Services 2 01-20-2004 06:09 AM
Unhandled exception: Server did not recognize the value of HTTP Header SOAPAction Hazzard ASP .Net Web Services 3 09-13-2003 01:51 PM
Server did not recognize the value of HTTP Header SOAPAction Juan Rodriguez ASP .Net Web Services 0 08-28-2003 02:44 PM



Advertisments