My webservice gives expected output when run in debugger in visual studio. I hosted my service in IIS 6.0. When I browse to http://mywebserver/Service1/Service1.svc, it shows the test page with link to t needs to ewsdl. But when I send a SOAP Request to the service I get error. As suggested I am copying headers from Fiddler. Please suggest what needs to be corrected, or if you need more information for troubleshooting. Thanks.

POST /Service1 HTTP/1.1
Content-Type: text/xml; Charset=UTF-8
User-Agent: XML Spy
SOAPAction: "http://tempuri.org/IService1/GetOrderMsgInfo"
Host: MyWebServer
Content-Length: 414
Connection: Keep-Alive
Pragma: no-cache

http://schemas.xmlsoap.org/soap/envelope/" xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
 
  http://tempuri.org/">
   HIS10-001946
  

 

HTTP/1.1 405 Method Not Allowed
Allow: OPTIONS, TRACE, GET, HEAD
Content-Length: 1564
Content-Type: text/html
Server: Microsoft-IIS/6.0
MicrosoftOfficeWebServer: 5.0_Pub
X-Powered-By: ASP.NET
Date: Sun, 03 Oct 2010 18:17:15 GMT

http://www.w3.org/TR/html4/strict.dtd">
The page cannot be displayed


The page cannot be displayed


The page you are looking for cannot be displayed because an invalid method (HTTP verb) was used to attempt access.


Please try the following:



  • Contact the Web site administrator if you believe that this request should be allowed.

  • Make sure that the Web site address displayed in the address bar of your browser is spelled and formatted correctly.


HTTP Error 405 - The HTTP verb used to access this page is not allowed.
Internet Information Services (IIS)




Technical Information (for support personnel)



  • Go to http://go.microsoft.com/fwlink/?linkid=8180">Microsoft Product Support Services and perform a title search for the words HTTP and 405.

  • Open IIS Help, which is accessible in IIS Manager (inetmgr),
     and search for topics titled Setting Application Mappings, Securing Your Site with Web Site Permissions, and About Custom Error Messages.

------------------------------------------------------------------