系统 dll 出现故障然后服务崩溃
我们的一项书面服务出现了一种奇怪的失败模式。我们会从系统 dll 中得到一个错误,然后大约一分钟后我们的服务就会崩溃,无论有没有未处理的异常。
我们将从 .Net 运行时错误报告中收到以下错误模块消息之一:
faulting module kernel32.dll, version 5.1.2600.5781
faulting module ntdll.dll, version 5.1.2600.5755
faulting module clbcatq.dll, version 2001.12.4414.700
超过 30 秒(但不到一分钟)后,我们可能会或可能不会收到如下异常:
System.Runtime.InteropServices.SEHException
System.AccessViolationException
exception in a MSDTC related component
System.Globalization.CultureNotFoundException
有人见过吗这种延迟/配对行为?这两个错误都会报告给事件查看器。这种情况只发生在一些物理上较旧的 XP 生产系统上,而不会发生在开发系统上。
We've got a weird pattern of failure in one of our written services. We'll get a fault out of a system dll then a minute or so later our service will crash with or without a unhandled exception.
We'll get one of the following faulted module messages from .Net runtime error reporting:
faulting module kernel32.dll, version 5.1.2600.5781
faulting module ntdll.dll, version 5.1.2600.5755
faulting module clbcatq.dll, version 2001.12.4414.700
More than 30 seconds (but less than a minute) later we may or may not get an exception like:
System.Runtime.InteropServices.SEHException
System.AccessViolationException
exception in a MSDTC related component
System.Globalization.CultureNotFoundException
Has anyone seen this delayed/paired behavior? Both errors are reported to the event viewer. This only occurs on some physically-older XP production systems, never in dev.
如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱,如果其他用户或者作者回复了您的评论,将不能在第一时间通知您!
发布评论