Symptom

When protecting SQL Server 2008 R2 services, the “SQL Server Reporting Services (MSSQLSERVER)” may be selected as an optional protected service. However, if the time required to start this service exceeds the default Windows service timeout, you may get Error 1053, the service may fail to start and the LifeKeeper for Windows resource in-service operation will fail.

Solution

This problem may be related to system performance and configuration issues. The recommended action is to not protect this service. However, if it must be protected, the following registry setting will extend the time available for services to start. In the “HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control” Registry key, add a “ServicesPipeTimeout” value as a DWORD, and set the value to 60000 (decimal, = 60 secs.).

Feedback

Was this helpful?

Yes No
You indicated this topic was not helpful to you ...
Could you please leave a comment telling us why? Thank you!
Thanks for your feedback.

Post your comment on this topic.

Post Comment