Did you create the wsdl yourself, or did vs.net create it? Were you able to
test the web service project directly and call the webmethods and have them
work?


[quoted text, click to view]

Greetings Manika,

If you load the WSDL document in IE, at the bottom of the WSDL file,
does the location attribute of the soap:address element for the web
service match the URL entered into IE? Specifically, are there any
extra tokens appended to the server name?

The following are the elements I'm referring to:

<wsdl:service name="MyService">
<documentation/>
<wsdl:port name="MyServiceSoap" binding="tns:MyServiceSoap">
<soap:address
location="http://localhost//MyWebServices/MyService.asmx"/>
</wsdl:port>
</wsdl:service>

I have seen this error occur when the web server hosting the web
services is accessed through ISA server, and the administrators have
chosen to use host headers (with a slightly different server name) to
resolve the HTTP requests to the physical web server.

As a workaround, you should still be able to use the command line
wsdl.exe tool to create/update the web reference, as follows:

http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cptools/html/cpgrfWebServicesDescriptionLanguageToolWsdlexe.asp

HTH.

Cheers,
Matt