<div>
Can you browse to the web service via Internet Explorer or Firefox? 
 
Does your web service have any references to other web services i.e. web services that may be installed on your development machine but not the web server?
</div>

<div>
Yes, i can browse... 
 
I don't have any reference. When I add a simple hello world web service, I still get an error. 

</div>

<div>
Do you access external URLs through a proxy server? 
 
If so, add the following to your web.config: 
 

<pre><code class="code-1 nolinks" id="code-263608">&lt;system.net&gt;
 &lt;defaultProxy&gt;
 &lt;proxy usessystemdefault=&quot;False&quot; proxyaddress=&quot;http://your-proxy-name.domain.com:port-number-if-any&quot; bypassonlocal=&quot;True&quot; autoDetect=&quot;False&quot; /&gt;
 &lt;/defaultProxy&gt; 
&lt;/system.net&gt;
</code></pre>
</div>

<div>
Hello, 
 
I think that the problem is with link in wsdl file. The end of this file looks like this: 
 
&lt;wsdl:service name=&quot;Service&quot;&gt; 
- &lt;wsdl:port name=&quot;WSHttpBinding_IService&quot; binding=&quot;tns:WSHttpBinding_IService&quot;&gt; 
&nbsp; &lt;soap12:address location=&quot;<a href="http://MACHINE_NAME/TestWCFService/Service.svc" rel="ugc">http://MACHINE_NAME/TestWCFService/Service.svc</a>&quot; /&gt; 
- &lt;wsa10:EndpointReference&gt; 
&nbsp; &lt;wsa10:Address&gt;<a href="http://MACHINE_NAME/TestWCFService/Service.svc" rel="ugc">http://MACHINE_NAME/TestWCFService/Service.svc</a>&lt;/wsa10:Address&gt; 
- &lt;Identity xmlns=&quot;<a href="http://schemas.xmlsoap.org/ws/2006/02/addressingidentity" rel="ugc">http://schemas.xmlsoap.org/ws/2006/02/addressingidentity</a>&quot;&gt; 
&nbsp; &lt;Dns&gt;localhost&lt;/Dns&gt; 
&nbsp; &lt;/Identity&gt; 
&nbsp; &lt;/wsa10:EndpointReference&gt; 
&nbsp; &lt;/wsdl:port&gt; 
&nbsp; &lt;/wsdl:service&gt; 
 
where the MACHINE_NAME is correct machine name, but there has to be an IP address including port number to the server in format XXX.XX.XXX.XXX:XXXXX. 
 
If I put this IP address in web.config file for endpoint like this 
 
&lt;endpoint address=&quot;<a href="http://XXX.XX.XXX.XXX:XXXXX/TestWCFService/Service.svc" rel="ugc">http://XXX.XX.XXX.XXX:XXXXX/TestWCFService/Service.svc</a>&quot; binding=&quot;wsHttpBinding&quot; contract=&quot;IService&quot;&gt; 
 
and open this link in web browser there is an error 
 
&quot;No protocol binding matches the given address '<a href="http://XXX.XX.XXX.XXX:XXXXX/TestWCFService/Service.svc'" rel="ugc">http://XXX.XX.XXX.XXX:XXXXX/TestWCFService/Service.svc'</a>. Protocol bindings are configured at the Site level in IIS or WAS configuration&quot; 
 
I also found on this link <a href="http://forums.asp.net/p/1096811/1659596.aspx" rel="ugc">http://forums.asp.net/p/1096811/1659596.aspx</a>&nbsp;that I have to configure host header on web site. I also tried that but without result. I can't write my real IP address including port number in host name field. 
 
Any suggestions? 

</div>

<div>
Can you post the bindings and services sections of your web.config pls
</div>

<div>
Here are settings that works on localhost 
 
&lt;system.serviceModel&gt; 
&nbsp; &nbsp; &nbsp; &nbsp; &lt;services&gt; 
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &lt;service behaviorConfiguration=&quot;mexBehavior&quot; name=&quot;WCFService.Service1&quot;&gt; 
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &lt;endpoint address=&quot;&quot; binding=&quot;basicHttpBinding&quot; contract=&quot;WCFService.IService1&quot; listenUriMode=&quot;Explicit&quot; /&gt; 
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &lt;/service&gt; 
&nbsp; &nbsp; &nbsp; &nbsp; &lt;/services&gt; 
&nbsp; &nbsp; &nbsp; &nbsp; &lt;behaviors&gt; 
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &lt;serviceBehaviors&gt; 
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &lt;behavior name=&quot;ServiceBehavior&quot;&gt; 
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &lt;serviceMetadata httpGetEnabled=&quot;true&quot;/&gt; 
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &lt;serviceDebug includeExceptionDetailInFaults=&quot;false&quot;/&gt; 
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &lt;/behavior&gt; 
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &lt;behavior name=&quot;mexBehavior&quot;&gt; 
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &lt;serviceMetadata httpGetEnabled=&quot;true&quot;/&gt; 
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &lt;/behavior&gt; 
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &lt;/serviceBehaviors&gt; 
&nbsp; &nbsp; &nbsp; &nbsp; &lt;/behaviors&gt; 
&nbsp; &nbsp; &lt;/system.serviceModel&gt;&lt;system.serviceModel&gt; 
&nbsp; &nbsp; &nbsp; &nbsp; &lt;services&gt; 
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &lt;service behaviorConfiguration=&quot;mexBehavior&quot; name=&quot;WCFService.Service1&quot;&gt; 
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &lt;endpoint address=&quot;&quot; binding=&quot;basicHttpBinding&quot; contract=&quot;WCFService.IService1&quot; listenUriMode=&quot;Explicit&quot; /&gt; 
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &lt;/service&gt; 
&nbsp; &nbsp; &nbsp; &nbsp; &lt;/services&gt; 
&nbsp; &nbsp; &nbsp; &nbsp; &lt;behaviors&gt; 
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &lt;serviceBehaviors&gt; 
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &lt;behavior name=&quot;ServiceBehavior&quot;&gt; 
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &lt;serviceMetadata httpGetEnabled=&quot;true&quot;/&gt; 
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &lt;serviceDebug includeExceptionDetailInFaults=&quot;false&quot;/&gt; 
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &lt;/behavior&gt; 
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &lt;behavior name=&quot;mexBehavior&quot;&gt; 
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &lt;serviceMetadata httpGetEnabled=&quot;true&quot;/&gt; 
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &lt;/behavior&gt; 
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &lt;/serviceBehaviors&gt; 
&nbsp; &nbsp; &nbsp; &nbsp; &lt;/behaviors&gt; 
&nbsp; &nbsp; &lt;/system.serviceModel&gt;
</div>

<div>
<div class="content wysiwyg-content">
Hello, I'm having a strange web service problem. Locally on my computer it works fine, but when I upload it to web server (IIS7) and try to add a reference to my VS Project, it returns me the following error: (see code below) 
Can anyone help me solve this? 

<pre><code class="code-1 nolinks" id="code-263568">The document was understood, but it could not be processed.
 - The WSDL document contains links that could not be resolved.
 - There was an error downloading 'http://foi-sql/z/WcfService1/WcfService1/Service1.svc?xsd=xsd0'.
 - The remote name could not be resolved: 'my-service'
Metadata contains a reference that cannot be resolved: 'http://...../Service1.svc?wsdl'.
There was no endpoint listening at http://.../Service1.svc?wsdl that could accept the message. This is often caused by an incorrect address or SOAP action. See InnerException, if present, for more details.
The remote server returned an error: (404) Not Found.
If the service is defined in the current solution, try building the solution and adding the service reference again.
</code></pre>
</div>
</div>

Hello, I'm having a strange web service problem. Locally on my computer it works fine, but when I upload it to web server (IIS7) and try to add a reference to my VS Project, it returns me the following error: (see code below)
Can anyone help me solve this?

Web Service Problem - remote server error

Windows Communication Foundation (WCF) is a tool used to implement and deploy a service-oriented architecture (SOA) to support distributed computing where services have remote consumers. It features a runtime and a set of APIs in the .NET Framework for building connected, service-oriented applications. Services typically have a WSDL interface (Web Services Description Language) that any WCF client can use to consume the service, regardless of which platform the service is hosted on. WCF implements many advanced Web services (WS) standards such as WS-Addressing, WS-ReliableMessaging, WS-Security, RSS Syndication Services, WS-Discovery, routing and better support for REST services.