Search code examples
wcfexceptionwcf-bindingsvctraceviewer

WCF There was an error reading from the pipe: The pipe has been ended. (109, 0x6d)

I'm having continuous exception on live server and performance issues.

After enabling trace service log in wcf config file I found 100 of same exceptions.

enter image description here

Basic Information

 Activity ID    {00000000-0000-0000-0000-000000000000}
Time    2019-08-26 19:59:44.7454
Level   Error
Source  System.ServiceModel
Process w3wp
Thread  55
Computer    PC3
Trace Identifier/Code   https://learn.microsoft.com/dotnet/framework/wcf/diagnostics/tracing/System-ServiceModel-Diagnostics-ThrowingException

Exception

System.IO.PipeException, System.ServiceModel, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089

Exception Type 

System.IO.PipeException, System.ServiceModel, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089

Message 

There was an error reading from the pipe: The pipe has been ended. (109, 0x6d).

Here is the code I'm using common code

public static WMC.Proxy.BLLService.BLLServiceClient GetBLLServiceClient()
        {
            var client = new WMC.Proxy.BLLService.BLLServiceClient(settings.GetBinding(settings.BLLServiceBinding), new EndpointAddress(settings.BLLServiceAddress));
            SetMaxGraphInItems(client);
            return client;
        }

How can I fix this?

Solution

  • After a long search on the internet, I found the issue might be relates to the Enum type, which caused serialization failure.
    https://social.msdn.microsoft.com/Forums/vstudio/en-US/ee75d768-fd80-4c2b-831e-1d6dd6d4dd17/there-was-an-error-reading-from-the-pipe-the-pipe-has-been-ended-109-0x6d?forum=wcf
    WCF NamedPipe CommunicationException - "The pipe has been ended. (109, 0x6d)."
    There are many factors contributing to this problem, including data contract, service contract irregularities. It boils down to the fact the there is something wrong with the serialization. Please refer to the below discussion, wish it is useful to you.
    http://gonetdotnet.blogspot.com/2014/07/solved-there-was-error-reading-from.html
    https://blogs.infosupport.com/there-was-an-error-reading-from-the-pipe-unrecognized-error/
    Feel free to let me know if the problem still exists.