WCF NamedPipe CommunicationException - “The pipe has been ended. (109, 0x6d).”

Question

I am writing a Windows Service with accompanying \"status tool.\" The service hosts a WCF named pipe endpoint for inter-process communication. Through the named pipe, the

Answer 1

This exception means there is a serialization problem on the server side.

This issue can be resolved by looking into the trace file (svclog). To turn tracing on use the following configuration:

In my case I was serializing a value that was not in the enum.