得到“无法识别的错误 109 (0x6d)"可以“固定"通过更改 web.config [英] Getting "Unrecognized error 109 (0x6d)" which can be "fixed" by changing web.config

问题描述

我有一个使用 WAS 在 IIS 中托管的 WCF 服务.当我尝试使用 net.tcp 绑定访问此服务时，出现以下错误:

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:

从管道读取错误:无法识别的错误 109 (0x6d).

There was an error reading from the pipe: Unrecognized error 109 (0x6d).

使用basicHttp时没有遇到问题.

When using basicHttp I do not encounter the problem.

奇怪的是，我可以通过随机更改 web.config 并保存它来修复"问题.直到我执行 IISReset 或应用程序池回收，问题才会消失.然后它再次被破坏，直到我再次更改(或只是保存)web.config...

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...

• 我已启用跟踪，但这只会出现无法识别的错误.
• 重新启动没有帮助.
• 我提高了 WCF 中的阈值，但这并没有改变任何东西.

合约真的很简单，没有复杂的类型，所以没有序列化问题.返回的消息大小是一个只有 12 个字符的字符串

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

推荐答案

看看这个...

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

在我的情况下，重新启动 net tcp 侦听器和端口共享服务会有所帮助.这篇文章也很好地概述了最可能的原因.

In my case restarting net tcp listener and port sharing service helped. The article has a nice overview of most likely causes too.

这篇关于得到“无法识别的错误 109 (0x6d)"可以“固定"通过更改 web.config的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！