Getting "Unknown error 109 (0x6d)", which can be "fixed" by changing web.config

Question

I have a WCF service hosted in IIS using WAS. When I try to access this service using the net.tcp binding, I get the following error:

A channel read error occurred: Unrecognized error 109 (0x6d).

When using basicHttp I do not encounter a problem.

It is strange that I can "fix" the problem by accidentally changing web.config and saving it. The problem just disappears until I run IISReset or Recycle Pool. Then it is interrupted until I change (or just save) web.config again ...

• I turned on tracking, but that just leads to an unrecognized error.
• Rebooting does not help.
• I increased the thresholds in WCF, but didn't change anything.

The contract is really very simple without complex types, so there are no problems with serialization. The size of the returned message is a 12-character string.

Answer 1

Take a look at this ...

http://blogs.msdn.com/b/joncole/archive/2010/06/29/smsvchost-exe-event-log-id-8-an-error-occurred-while-dispatching-a-duplicated-socket- this-handle-is-now-leaked-in-the-process.aspx

In my case, restarting the net tcp listener and the port sharing service helped. The article also has a good overview of the most likely causes.

Answer 2

I have the same error, and I found a solution for my business, try it and check if it resolved yours.

In my case, unrecognized data was transmitted through WCF. It was a counter that was not registered.

For example, (C #):

enum MyEnum { A = 1, B = 2 }

And then I use a MyEnum object with a value of 3 (any that does not exist in the listing). Therefore, WCF cannot understand this value and gave me this error.

Answer 3

If you use large messages, you can try changing the transfer mode from buffered to streaming: http://msdn.microsoft.com/en-us/library/ms731913.aspx

He solved our problems.

Hi

Answer 4

I got this error because I was returning a DataTable from my service call, and I did not set the TableName property.