WCF - The message could not be dispatched because the service at the endpoint address … is unavailable for the protocol of the address

Question

Ok, can I vent?? I am so sick and tired of this. I\'m working away most of the day and the WCF services are working great. Next time I run my app and make a WCF call, bam! th

Answer 1

Sounds Net.Tcp Listener Adapter service is being killed by some process or exception being throw by the web service putting the channel in a faulted state.

Have you tried setting the startup type of the service to automatic and recovery to restart service on first and second failure?

I doubt it very much that there is a bug in wcf net.tcp channel layer. If the listener is running and tcp socket no longer available i would suggest you look into the code especially around the exception handling strategy and have a peek into the iis request logs.

Answer 2

This issue hunts me for almost 3 years now but only happens sporadically. TCPView helped. I have killed SMSSvcHost.exe process and then restarted Net.Tcp Listener Adapter service. That cleared the issue. Not really a solution but at least, I don't have to resort to rebooting the server anymore.

Answer 3

Check in the AD the account used for running the Application Pool in IIS.

The Appplication pool may be running but will stop on 1st connection attempt if the account is disabled/locked/in need for a password change.

Answer 4

I had this issue. It would happen after each IIS reset (which happens as part of our deployment). The issue was resolved after restarting NetTcpPortSharing service (which also restarts Net.Tcp Listener Adapter service)

Answer 5

1. Open a command prompt
2. Navigate to c:\windows\microsoft.net\framework64\v4.0.30319
3. Register the service model using the command "ServiceModelReg.exe -r"

Credits go there http://kumaranbose.blogspot.be/2010/08/cryptic-wcf-nettcp-errors.html

Answer 6

I am not sure I have an answer but, you could identify the process that has the port open and that can help narrow the scope of the problem. I have used Sysinternals suite which has a TCPView. This proggy was helpful to me.

TCPView - http://technet.microsoft.com/en-us/sysinternals/bb897437