SOLUTION
When a service
starts, the service communicates to the Service Control Manager how long
the service must have to start (the time-out period for the service).
If the Service Control Manager does not receive a "service started"
notice from the service within this time-out period, the Service Control
Manager terminates the process that hosts the service. This time-out
period is typically less than 30 seconds. If you do not adjust this
time-out period, the Service Control Manager ends the process. To adjust
this time-out period, follow these steps:
IMPORTANT:
Incorrect use of the Microsoft Windows Registry Editor may cause
serious problems with your computer, up to and including general
operating system corruption and inability to boot. Registry editing
should only be performed by those who are sufficiently experienced in
the use of the registry editor application.
- Go to Start > Run > and type regedit
- Navigate to: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control
- With the control folder selected, right click in the pane on the right and select new DWORD Value
- Name the new DWORD: ServicesPipeTimeout
- Right-click ServicesPipeTimeout, and then click Modify
- Click Decimal, type '180000', and then click OK
- Restart the computer
CAUSE
The Microsoft Windows Service Control Manager controls the state (i.e., started, stopped, paused, etc.) of all installed Windows services. By default, the Service Control Manager will wait 30,000 milliseconds (30 seconds) for a service to respond. However, certain configurations, technical restrictions, or performance issues may result in the service taking longer than 30 seconds to start and report ready to the Service Control Manager.
By editing or creating the ServicesPipeTimeout DWORD value, the Service
Control Manager timeout period can be overridden, thereby giving the
service more time to start up and report ready to the Service.