Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

Background: We have a remote web server that has our web site and web service on it. We have access to this service and the site, but not the server directly as it is managed by another company.

The Problem: Our web services are operational and work fine, but we cannot connect to the web service because the WSDL specifies the soap address location as:


'Webserver' should be replaced with our site name:

Because of this error we cannot add web references in Visual Studio or use the current WSDL file. We have to manually edit the WSDL, disco, and map files so that can connect to the service.

We have notified the admins that manage this, but they have apparently not been able to find the solution to this issue. Is there a specific property that must be set in IIS or in the website? I know the WSDL is generated automatically on the server, but is there any code that we need to put in the web service on our end for this to work? Any help is appreciated.

share|improve this question

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.