Service operations fail with timeout

Issue encountered

When attempting to start, stop or pause a GFI Archiver service, one of the following error messages is encountered:

• Error 1053: The service did not respond to the start or control request in a timely fashion.
• Error 7000: The <ServiceName> failed to start due to the following error: The service did not respond to the start or control request in a timely fashion.
• Error 7009: Timeout (30000 milliseconds) waiting for the <ServiceName> service to connect.

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 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.

Solution

Create the ServicesPipeTimeout key in the registry. Backup the Registry before proceeding, as the incorrect use, can lead to serious problems.

To edit the Registry:

1. Go to Start > Run and type regedit.
2. Navigate to: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control
3. With the Control folder selected, right click in the pane on the right and select New > DWORD.
4. Name the new DWORD: ServicesPipeTimeout
5. Right-click the newly created ServicesPipeTimeout key, and click Modify.
6. Click Decimal, type 180000, and then click OK.
7. Restart the server.