CODEWITHSUNDEEP
wcf
Clarence Klopfstein
Clarence Klopfstein

Reputation: 4862

WCF Metadata reference cannot be resolved

I am having an issue where I can't add a service reference in Visual Studio 2010 via a URL.

I have my HOST file setup to resolve http://mydomain.com locally, and setup my web.config file to reference this url. However when I go to add a service reference by URL I get the following error:

Metadata contains a reference that cannot be resolved: 'http://mydomain.com/myservice.svc?wsdl'.

The WSDL document contains links that could not be resolved.

There was an error downloading 'http://mydomain.com/myservice.svc?xsd=xsd0'.

The underlying connection was closed: An unexpected error occurred on a receive.

Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host.

An existing connection was forcibly closed by the remote host

Metadata contains a reference that cannot be resolved: 'http://mydomain.com/myservice.svc'.

There was no endpoint listening at http://mydomain.com/myservice.svc 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.

The other URLS work fine: http://mydomain.com/myservice.svc?wsdl and http://mydomain.com/myservice.svc

Here is my web.config file:

<?xml version="1.0"?>
<configuration>

  <system.web>
    <compilation debug="true" targetFramework="4.0" />
  </system.web>
  <system.serviceModel>

    <services>
      <!-- Note: the service name must match the configuration name for the service implementation. -->
      <service name="FuncWS.Email" behaviorConfiguration="ServiceType" >
        <!-- Add the following endpoint.  -->
        <endpoint address="myservice.svc" binding="webHttpBinding" contract="FuncWS.IEmail"></endpoint>
        <!-- Note: your service must have an http base address to add this endpoint. -->
        <endpoint contract="IMetadataExchange" binding="mexHttpBinding" address="mex" />
        <host>
          <baseAddresses>
            <add baseAddress="http://mydomain.com"/>
          </baseAddresses>
        </host>
      </service>
    </services>
    <behaviors>
      <serviceBehaviors>
        <behavior name="ServiceType">
          <!-- To avoid disclosing metadata information, set the value below to false and remove the metadata endpoint above before deployment -->
          <serviceMetadata httpGetEnabled="true"/>
          <!-- To receive exception details in faults for debugging purposes, set the value below to true.  Set to false before deployment to avoid disclosing exception information -->
          <serviceDebug includeExceptionDetailInFaults="false"/>
        </behavior>
      </serviceBehaviors>
    </behaviors>
    <serviceHostingEnvironment multipleSiteBindingsEnabled="true" />
  </system.serviceModel>
  <system.webServer>
    <modules runAllManagedModulesForAllRequests="true"/>
  </system.webServer>
</configuration>

Upvotes: 4

Views: 19178

Answers (1)

Clarence Klopfstein
Clarence Klopfstein

Reputation: 4862

The solution to this problem is that IIS needs to have rights to the C:\Windows\Temp folder. Without this it can't generate the meta data needed.

Upvotes: 20

Related Questions