Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • SEARCH
  • Home
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 304391
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 12, 20262026-05-12T07:16:35+00:00 2026-05-12T07:16:35+00:00

I have developed an ASP.NET application that includes a WCF service. This service needs

  • 0

I have developed an ASP.NET application that includes a WCF service. This service needs to be consumed by third party applications. This service has worked fine while testing in my development environment. My development environment is using IIS 7.0 on Window 7 RC 1. However, I cannot use the service once it is in my staging / production environment. My staging / production environment is a Windows Server 2003, IIS 6 environment.

When I attempt to reference the service when it is in the IIS 6 environment, I receive an error that says:

Error: Cannot obtain Metadata
…

Interesting, I noticed a subtle, but I believe important, difference in my testing an staging/production environments.

In my test environment, I noticed that I can access the Service page via a url with the following template:

http://localhost/MyApp/services/myService.svc

I also noticed that in my test environment, I can see the WSDL information if I visit a url with the following template:

http://localhost/MyApp/services/myService.svc?wsdl

However, in my staging / production environment, I cannot see the WSDL information. Oddly enough, I can see the Service page though.

Here are the configuration settings related to my services in my production environment.

<system.serviceModel>
  <behaviors>
    <serviceBehaviors>
      <behavior name="myServiceBehavior">
        <serviceMetadata httpGetEnabled="true" />
        <serviceDebug includeExceptionDetailInFaults="false" />
      </behavior>
    </serviceBehaviors>
  </behaviors>

  <serviceHostingEnvironment aspNetCompatibilityEnabled="true"/>
  <services>
    <service behaviorConfiguration="myServiceBehavior" name="myService">
      <endpoint address="" binding="basicHttpBinding" contract="myService" />
      <endpoint address="mex" binding="mexHttpBinding" 
        contract="IMetadataExchange" />
    </service>
  </services>
</system.serviceModel>

Why would I be able to see the Service page but not the WSDL page in the Windows Server 2003 IIS 6.0 environment?

Thank you!

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-05-12T07:16:35+00:00Added an answer on May 12, 2026 at 7:16 am

    To add to Shiraz’s answer, the following MSDN article covers publishing service metadata in reasonable detail:

    Publishing Metadata Endpoints (MSDN Library)

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

I am looking at globalizing an application that I have developed in asp.net mvc.
I have a web application developed with ASP.net and C# that is running on
I am using asp.net MVC to develop an application that will have ajax interactions.
I have an ASP.NET application developed on my Vista box (IIS7). It works fine
I have two web applications and both are developed in ASP.NET. Now I want
I have developed an ASP.NET web application in Visual Studio 2008. I have an
I have developed a ASP.NET application,I have used sessions for parameter passing. I dont
I have a ASP.NET web application that uses Themes. Inside the theme directory are
i have developed a web application with asp.net and c#.net and i use sql
So, being an early adopter, I have developed an application based on SQLCE4, ASP.Net

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.