Windows服务错误-事件1001 Windows错误报告 [英] Windows Service error - Event 1001 Windows Error Reporting

查看:5426
本文介绍了Windows服务错误-事件1001 Windows错误报告的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我的Windows服务突然(!)无法启动.当我尝试启动它时,它
立即返回 并显示主题行中的错误.事件数据如下:

All of a sudden (!) my Windows Service wont start. When I try to start it, it
returns immediately with the error in the subject line. The event data is as follows:

Fault bucket , type 0
Event Name: CLR20r3
Response: Not available
Cab Id: 0
Problem signature:
P1: tcptunercollector.exe
P2: 1.0.0.0
P3: 4e3a9d71
P4: System.Configuration
P5: 2.0.0.0
P6: 4a275e0d
P7: 1a6
P8: 15a
P9: IOIBMURHYNRXKW0ZXKYRVFN0BOYYUFOW
P10:
Attached files:
C:\Windows\Temp\WER93D4.tmp.WERInternalMetadata.xml
C:\Windows\Temp\WER93D5.tmp.hdmp
C:\Windows\Temp\WERA7AC.tmp.mdmp
These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_tcptunercollecto_2237e423646d0acc8ebaff0aa4bce62dbc1192_cab_88c1a885
Analysis symbol:
Rechecking for solution: 0
Report Id: 9a729c80-bea3-11e0-9d85-005056ba0076
Report Status: 4





同时,Windows系统日志显示服务未及时响应启动或控制请求".它还说:在等待SDV收集器连接时已达到超时(30000毫秒)."

这不是真的.它立即返回,并且永远不会执行在我的OnStart方法中写入的事件日志.

它正在Windows Server 2008 R2上运行.

另外,这在我的Windows XP开发箱上也可以正常运行.

我已经搜索了这些错误,但是大多数人都认为该服务实际上根本没有响应.

当我尝试启动服务时,会立即发生此错误.

如果这不是服务器,我将尝试重新启动它,但现在我宁愿
尝试并理解问题.

在此先感谢您的任何建议.





At the same time, the Windows System log says that "The service did not respond to the start or control request in a timely fashion". It also says "A timeout was reached (30000 milliseconds) while waiting for the SDV collector to connect".

This is NOT true. It returns immediately, and an event log write in my OnStart method never gets executed.

This is running on Windows Server 2008 R2.

Also, this runs fine on my Windows XP development box.

I have searched for these errors, but most assume that the service is really simply not responding.

This error happens immediately when I try to start the service.

If this wasn''t a server, I would try rebooting it, but for now I would rather
try and understand the problem.

Thanks in advance for any suggestions.

推荐答案

对于您失败的原因,我无能为力,但可以为您提供超时报告.

每当服务在启动时引发异常时,您将始终收到该错误消息.服务启动不关心由于循环或异常而导致响应失败,它仅关心是否成功完成启动.从OnStart命令返回时,基类将返回指示您已成功启动的代码.

我通常要做的是启动跟踪监视器(例如从SysTools中获取),并在执行代码时输入trace.WriteLine命令.这有助于告诉我我在哪里爆炸.

但是...看您所显示的内容,您班级的签名与注册时的签名不同.您是否制作了新版本并将其复制到服务器上?我相信,对于我的服务,我总是会进行卸载和安装,以确保签名与服务器上显示的内容匹配.
I cannot help you much on the cause of your failure but can help you with the timeout report.

Whenever a service is in startup and throws an exception, you will always get that error message. Service startup does not care if you failed to respond due to a loop or an exception, it just cares as to whether or not you are completing startup successfully. When you return from your OnStart command the base class returns the code that indicates you started up successfully.

What I usually do is pull up a trace monitor (like from SysTools) and throw in trace.WriteLine commands as I progress thru the code. That helps to tell me where I blew up.

However...looking at what you displayed, the signature for you class is different from what it was when it was registered. Did you make a new version and just copy it onto the server? I believe for my services I always did an uninstall and install to ensure the signature matched what is being put out on the server.


这篇关于Windows服务错误-事件1001 Windows错误报告的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆