获得“无法识别的错误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
推荐答案
我遇到了同样的错误并找到了我的案例的解决方案,尝试一下,看看它是否解决你的问题。
I have got the same error and found a solution to my case, try it out and check if it resolve yours.
在我的情况下,有一个无法识别的数据通过WCF传递。这是一个未注册的普查员。
In my case, there was a unrecognized data being passed through WCF. It was a enumerator that was not registered.
例如(c#):
enum MyEnum
{
A = 1,
B = 2
}
然后我使用值为3的MyEnum对象(枚举中不存在的任何对象)。所以,WCF无法理解这个值并给了我这个错误。
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.
这篇关于获得“无法识别的错误109(0x6d)”它可以是“固定的”,也可以是“固定的”。通过更改web.config的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!