I have a WCF service hosted in IIS using WAS. When I try to access this service using a net.tcp binding I get the following error:
There was an error reading from the pipe: Unrecognized error 109 (0x6d).
When using basicHttp I do not encounter the problem.
The strange thing is that I can "fix" the problem by randomly changing the web.config and saving it. The problem just vanishes until I do an IISReset or an Application Pool Recycle. It is then broken again until I change (or just save) the web.config again...
The contract is really really simple with no complex types, so no serialization problems. The return message size is a string of only 12 characters
Have a look at this...
https://docs.microsoft.com/en-ca/archive/blogs/joncole/smsvchost-exe-event-log-id-8-an-error-occurred-while-dispatching-a-duplicated-socket-this-handle-is-now-leaked-in-the-process
In my case restarting net tcp listener and port sharing service helped. The article has a nice overview of most likely causes too.
I have got the same error and found a solution to my case, try it out and check if it resolve yours.
In my case, there was a unrecognized data being passed through WCF. It was a enumerator that was not registered.
E.g (c#):
enum MyEnum
{
A = 1,
B = 2
}
And then I use a MyEnum object with value 3 (any that dont exist in enum). So, WCF cant understand this value and gave me this error.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With