Windows could not start service on Win Server 2008 R2 SP1 (Error 1053)

Error 1053: The service did not respond to the start or control request in a timely fashion

Applicable for:

This exercise is tried in Window XP, Windows Server 2008 R2 Entp. SP1

Cause:-

I have come across two reasons this issue.

1. Service taking time to start and the timeout period at windows registry level is configured as either very less or no timeout setting.

2. No proper access to Domain\user.

Solutions:-

If we have 1st as the reason perform below steps.

1. Click Start, click Run, type regedit, and then click OK.
2. Locate and then click the following registry subkey:HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control
3.In the right pane, locate the ServicesPipeTimeout entry.If the ServicesPipeTimeout entry does not exist, you must create it by "On the Edit menu, point to New, and then click DWORD Value" "Type ServicesPipeTimeout, and then press ENTER.".
4. Right-click ServicesPipeTimeout, and then click Modify.
5.Click Decimal, type 60000, and then click OK. i.e 60 sec.
6. Restart the computer.

If we have 2nd as a reason then check for below Access rights.

Normally when we create a service with a particularity user/Domain account that user becomes administrator of that folder and application files(for example .exe, .bat) in that folder. Compare the properties of the .exe or the .bat files which the window service is invoking for both the users one which created the service and other user which is either different domain user or localadmin user. If all the properties are fine then. Particularly check the advanced attributes you may find that the user who installed the service files may have Encrypt Contents to Secure Data as checked. Un-check this for all the users and then try. It will work.

Good Luck.