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 8466659
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: June 10, 20262026-06-10T15:24:23+00:00 2026-06-10T15:24:23+00:00

When I run my WCF in normal mode it works, but when I run

  • 0

When I run my WCF in normal mode it works, but when I run through the Azure Computer Emulator on my local PC, the port numbers are different. For instance, the WCF page opens up in under the address: http://localhost:81/ServiceName1.svc, but the WSDL address says

You can also access the service description as a single file:

http://pc-name1:82/ServiceName1.svc?singleWsdl

When I try to connect using WCF test client, it is not working when I try to fetch the address http://localhost:81/ServiceName1.svc or the address http://pc-name1:82/ServiceName1.svc

Do you know what might be happening? Has anyone noticed this when using the Azure emulator?

  • 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-06-10T15:24:25+00:00Added an answer on June 10, 2026 at 3:24 pm

    Have you gone through the Hosting WCF within Windows Azure exercise? This behaviour is explained. You need an update to the WCF – KB981002- WCF: Hotfix rollup update, which will add a special behavior for your WCF services:

    7.About the System.ServiceModel configuration above:

    1. For this example we are exposing a metadata exchange (MEX) endpoint in addition to the service main endpoint. This will expose
      the service metadata and thus allow service references to be added to
      this service in Visual Studio.
    2. The useRequestHeadersForMetadataAddress behavior is a special behavior that is defined in KB981002- WCF: Hotfix rollup update. It
      allows WCF to serve correct metadata behind load balancers. Windows
      Azure web roles are load balanced between one or more physical
      servers.
    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

When I run my WCF service on my local machine, it works fine. When
Has anyone managed to run wcf successfully in 2.0 integrated mode on IIS7 when
Hi I created WCF service and run it on WebDevelopmentServer. It works fine. Than
Is there way to run self host a WCF service with ServiceHost on local
I have an ADO.NET Data service that I run through WCF: public class AdminService
I have a pretty simple WCF service set up to run in an Azure
I created my WCF project and it works fine when I just run it
I'm trying to build out a WCF service but I've run into a blocking
I have an WCF it is run Successfully when i run it my local
I have a WCF service that is configured to run for a high port

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.