restart/iisreset disables NET.TCP protocol ?

Question

I'm hosting a WCF service in IIS7 on Windows Server 08, sp2. The service is hosted as its own website and is exposed via a NET.TCP endpoint. The service works perfectly until a restart/iisreset command is issued.

After restart or iisreset, when I make any service call, I receive the following error: 'System.ServiceModel.EndpointNotFoundException: The message could not be dispatched because the service at the endpoint address 'net.tcp://[website]/[service_name].svc' is unavailable for the protocol of the address.. '

The server's event log shows the following error: 'An error occurred while trying to read and instantiate the configured ProcessHandlerType. Exception: System.ArgumentException Message: Unknown protocol ID 'NET.TCP'. StackTrace: at System.Web.Hosting.ProcessHost.StartProcessProtocolListenerChannel(String protocolId, IListenerChannelCallback listenerChannelCallback) '

Question: How do I fix this? Why is the NET.TCP protocol disabled after iisreset? Is it a bug? Am I missing some configuration?

IIS setup details: - Server 08 and 08 R2 - Bindings: http, NET.TCP (808:*) - EnabledProtols: http,NET.TCP. - The identity for the site's appPool is set to a specific user.

Sample code available here: http://drop.io/wcfTcpSampleService

Thanks

Answer 1

Do you actually need to do a full IISRESET? I believe the "modern" recommended method when needing to have a web-hosted app fully restart is recycling the app pool as thus: iisapp /a <App_Pool_ID> /r (Windows 2003) or appcmd recycle apppool /apppool.name:<App_Pool_Name> (Windows 2008).

Answer 2

Can you use different ports for NET.TCP and HTTP protocols?

Update

On my PC everything works as it should, and I have tried both restart and iisreset. I have uploaded in the same place your project including binaries (used Visual Web Developer 2010 Express), and a screenshot of IIS settings. The app pool is set to .NET 4.0 integrated.

Answer 3

What versions of .NET do you have (or have you had) installed?

I had a very similar issue when going from .NET 4 RC to RTM as the TCP services were using dlls from the RC install (which no longer existed) causing the services to stop.

Answer 4

Solved. The problem is case-sensitivity. In the AdvancedSettings of the web application, the EnabledProtocols field must be lower case ie 'net.tcp' (I just learned this from MS support). I assumed (foolishly) that 'NET.TCP' should be upper case because of the description of the EnabledProtocols field ("...add those values, such as NET.TCP...").

The strange, unknown issue is why it would work with 'NET.TCP' the first time, but that's another issue.

Thanks for all you help everyone.