When you start a computer that is running Windows Server 2003, Windows Server 2008, or Windows Server 2008 R2, an Archive Shuttle service does not start, and the following error events appear in the Application log:
Event 1

Event Type: Error
Event Source: Service Control Manager
Event Category: None
Event ID: 7000

The ArchiveShuttleServiceName service failed to start due to the following error:
The service did not respond to the start or control request in a timely fashion.
Event 2

Event Type: Error
Event Source: Service Control Manager
Event Category: None
Event ID: 7011

Timeout (30000 milliseconds) waiting for a transaction response from the ArchiveShuttleServiceName service.
Event 3

Event Type: Error
Source: Service Control Manager
Event ID: 7009
Task Category: None

A timeout was reached (30000 milliseconds) while waiting for the ArchiveShuttleServiceName service to connect.
Default time out is set to 30,000 milliseconds (30 seconds) when starting services, but it could take more than that on older versions of Windows Server. To work around it, modify the registry to increase the default time-out value for the service control manager. To increase this value to 60 seconds or higher, follow these steps:

  1. Click Start, click Run, type regedit, and then click OK.
  2. Locate and then click the following registry subkey:
  3. In the right pane, locate the ServicesPipeTimeout entry.Note If the ServicesPipeTimeout entry does not exist, you must create it. To do this, follow these steps:
    1. On the Edit menu, point to New, and then click DWORD Value.
    2. Type ServicesPipeTimeout, and then press ENTER.
  4. Right-click ServicesPipeTimeout, and then click Modify.
  5. Click Decimal, type 60000, and then click OK.This value represents the time in milliseconds before a service times out.
  6. Restart the computer.

More details in Microsoft technote.

Print Friendly, PDF & Email