Cruise Control.Net 服务器错误：错误 1053：服务未及时响应启动或控制请求
我最近无法重新启动 CruiseControl.NET 服务器服务。
不过控制台版本运行正常。
当我运行该服务时，出现以下错误：
无法在本地计算机上启动 CruiseControl.NET 服务器服务
错误 1053：该服务未及时响应启动或控制请求
下面的文本显示了我的应用程序中的应用程序错误事件视图：
Event Type: Error
Event Source: Application Error
Event Category: (100)
Event ID: 1000
Date: 13/10/11
Time: 03:29:59
User: N/A
Computer: AUTHEWS01-V
Description:
Faulting application ccservice.exe, version 1.6.7981.1, faulting module kernel32.dll, version 5.2.3790.4480, fault address 0x0000bef7.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 41 70 70 6c 69 63 61 74 Applicat
0008: 69 6f 6e 20 46 61 69 6c ion Fail
0010: 75 72 65 20 20 63 63 73 ure ccs
0018: 65 72 76 69 63 65 2e 65 ervice.e
0020: 78 65 20 31 2e 36 2e 37 xe 1.6.7
0028: 39 38 31 2e 31 20 69 6e 981.1 in
0030: 20 6b 65 72 6e 65 6c 33 kernel3
0038: 32 2e 64 6c 6c 20 35 2e 2.dll 5.
0040: 32 2e 33 37 39 30 2e 34 2.3790.4
0048: 34 38 30 20 61 74 20 6f 480 at o
0050: 66 66 73 65 74 20 30 30 ffset 00
0058: 30 30 62 65 66 37 00bef7
我希望得到一些帮助，干杯
I'm unable to re-start my CruiseControl.NET Server Service lately.
The console version runs alright though.
I get the error below when I run the service:
Could not start the CruiseControl.NET Server service on Local Computer
Error 1053: Ther service did not respond to the start or control request in a timely fashion
The text below dispalys ther application error in my event view:
Event Type: Error
Event Source: Application Error
Event Category: (100)
Event ID: 1000
Date: 13/10/11
Time: 03:29:59
User: N/A
Computer: AUTHEWS01-V
Description:
Faulting application ccservice.exe, version 1.6.7981.1, faulting module kernel32.dll, version 5.2.3790.4480, fault address 0x0000bef7.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 41 70 70 6c 69 63 61 74 Applicat
0008: 69 6f 6e 20 46 61 69 6c ion Fail
0010: 75 72 65 20 20 63 63 73 ure ccs
0018: 65 72 76 69 63 65 2e 65 ervice.e
0020: 78 65 20 31 2e 36 2e 37 xe 1.6.7
0028: 39 38 31 2e 31 20 69 6e 981.1 in
0030: 20 6b 65 72 6e 65 6c 33 kernel3
0038: 32 2e 64 6c 6c 20 35 2e 2.dll 5.
0040: 32 2e 33 37 39 30 2e 34 2.3790.4
0048: 34 38 30 20 61 74 20 6f 480 at o
0050: 66 66 73 65 74 20 30 30 ffset 00
0058: 30 30 62 65 66 37 00bef7
I'd appreciate some help, cheers
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
我最常看到 CCNET 服务失败，要么是因为运行该服务的用户凭据无效，要么是因为配置已严重损坏，以至于 CCNET 无法在启动时处理它。
因此，首先检查服务用户身份 - 该用户是否仍然有效？密码正确吗？
然后通过 CCValidator 运行您的配置，以防万一命令行版本忽略了某些内容但导致服务崩溃。还要比较应用程序配置文件 - 服务配置中的某些内容可能会被破坏，但命令行配置不会被破坏。
I most commonly see the CCNET service fail like that either because the user credentials which the service is running under are invalid, or because the configuration has been broken badly enough that CCNET can't process it at startup.
So check the service user identity first - is the user still a valid one? Is the password right?
Then run your config through CCValidator just in case there's something in there that the commandline version is ignoring but is tripping the service up. Also compare the application config files - something could be broken in the service config but not the commandline config.
就我而言，这是因为服务器上未安装 .net Framework 2.0/3.5 :)
通过安装该框架来修复。
In my case it was because .net framework 2.0/3.5 was not installed on a server :)
Fixed by installing that framework.