WCF distributed development Common error resolution (9)

WCF distributed development Common error Resolution (9): No endpoint monitoring, There was no endpoint listening at

When we add the service metadata address, look for the metadata service, and do the deserialization operation. There is an error: No endpoint Listening metadata contains a reference that cannot to be resolved: ' Net.tcp://localhost:9004/mex '.

There is no endpoint listening at Net.tcp://localhost:9004/mex this could the message. This is often caused by a incorrect address or SOAP action. InnerException, if present, for more details.

If the service is defined into the current solution, try building the solution and adding the service reference. As shown in the picture:

Possible causes: This error is due to

1. Metadata Service address error caused.

2. The managed host did not start.

Solution:

1. Configure meta data exchange endpoints, such as <endpoint address= "Mex" binding= "mexHttpBinding" contract= "IMetadataExchange"/>

2. Running the hosting host;

3. Enter the corresponding meta data exchange endpoint address. Note that the HTTP Metadata Exchange protocol in the example, we query the metadata service must pay attention to the binding protocol.

Note: SkyPan found this error, thank you, here specifically sorted out for your reference.

4. In addition, this error is most likely to occur if you deploy an IIS managed WCF service. The main point is that the service address after deployment resulted in an address error: Some netizens discussed the issue in the WCF Chinese Forum. We can refer to:

CSQ333: Consult in the development of the time is OK, deployed to the WIN2003 after the error occurred:

Http://social.msdn.microsoft.com/Forums/en-US/wcfzhchs/thread/bf879ce5-aff5-484f-b6ed-65ee6a0c69aa.

Ninetynine_lipei: The client invokes the test of the path problem of the endpoint address of the service (IIS managed WCF Service program):

Http://social.msdn.microsoft.com/Forums/en-US/wcfzhchs/thread/4ce24ea1-ece5-423d-b07b-a39692895b72