-
Title
Rapid Recovery Core/Agent service does not start. Windows Events 7000, 7009, and/or 7011 are logged. -
Description
Rapid Recovery Core or Agent service is not starting up when set for Automatic (Delayed Start). The following Windows System Event entries can be found:
Log Name: System
Source: Service Control Manager
Date: 5/19/2019 3:28:10 PM
Event ID: 7000
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: core64.quest.com
Description:
The Rapid Recovery Core Service service failed to start due to the following error:
The service did not respond to the start or control request in a timely fashion.
Log Name: System
Source: Service Control Manager
Date: 5/19/2019 3:28:10 PM
Event ID: 7009
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: agent64.quest.com
Description:
A timeout was reached (30000 milliseconds) while waiting for the RapidRecoveryAgent service to connect.In the case of the the Core, this can cause a "dirty" shutdown in the sense that the Core will need to perform an extended repository check because the service stopped before it had time to fully start.
-
Cause
This issue occurs when the server is taking a long amount of time to start the dependencies of the Core or Agent service. If the time allotted is exceeded when starting a service, then the Service Control Manager times out. System resources (e.g. memory) might be limited for the amount of service scheduled to start with Windows. -
Resolution
Issue could be resolved by improving the hardware (e.g. add or assign more memory, replace with faster disk, etc.) or extending services startup timeout. Modify the registry to increase the default time-out value for the service control manager referenced in Microsoft KB922918. To increase this value to 2 mins (120 seconds), follow these steps:
- Click Start then Run, type regedit, and then click the [OK] button.
- Locate and then click the following registry subkey:
- HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control
- In the right pane, locate the ServicesPipeTimeout entry. If the entry does not exist, create the ServicesPipeTimeout key. To do this, follow these steps:
- On the Edit menu, point to New, and then click DWORD Value.
- Type ServicesPipeTimeout, and then press ENTER
- Right-click ServicesPipeTimeout, and then click Modify.
- Click Decimal, type 120000, and then click OK. This value represents the time in milliseconds before a service times out.
- Note: 120000 milliseconds (2 minutes) is equal to what the default configuration should be. You might find out that increasing this value to 300000 (5 minutes) may be more suitable.
- Restart the computer.
Windows Registry Disclaimer:Quest does not provide support for problems that arise from improper modification of the registry. The Windows registry contains information critical to your computer and applications. Make sure you back up the registry before modifying it. For more information on the Windows Registry Editor and how to back up and restore it, refer to Microsoft Article ID 256986 “Description of the Microsoft Windows registry” at Microsoft Support.
-
Additional Information
https://learn.microsoft.com/en-us/troubleshoot/windows-server/system-management-components/service-not-start-events-7000-7011-time-out-error