Return
-
Title
Rapid Recovery VMware Proxy service does not start, and events 7000, 7009, and/or 7011 are logged -
Description
Rapid Recovery VMware Proxy service is not starting up correctly automatically when it's set for auto(delayed) start. The following System Event Errors are seen on the core server:
Log Name: System
Source: Service Control Manager
Date: 6/28/2016 12:31:20 AM
Event ID: 7009
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: win2012r2-rrcr1
Description:
A timeout was reached (30000 milliseconds) while waiting for the Dell Data Protection | Rapid Recovery VMware Proxy Service service to connect.
Log Name: System
Source: Service Control Manager
Date: 6/28/2016 12:31:20 AM
Event ID: 7000
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: win2012r2-rrcr1
Description:
The Dell Data Protection | Rapid Recovery VMware Proxy 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. -
Cause
This issue occurs when the core server is taking a longer amount of time to start the Rapid Recovery VMware Proxy service. If the time allotted is exceeded when starting Rapid Recovery VMware Proxy service attempts to start automatically, then the Service Control Manager will time-out.
In severe CPU contention cases especially for Rapid Recovery core installed in virtual environments, manually starting the service later may not even work as starting the Rapid Recovery VMware Proxy service consistently needs more than 30 seconds to correctly start up.
-
Resolution
To resolve this issue, modify the registry to increase the default time-out value for the service control manager referenced in the Microsoft KB:
http://support.microsoft.com/kb/922918
To increase this value to 2 mins (120 seconds), follow these 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. Note If the ServicesPipeTimeout entry does not exist, you must create it. To do this, follow these steps:
a. On the Edit menu, point to New, and then click DWORD Value.
b. Type ServicesPipeTimeout, and then press ENTER
4. Right-click ServicesPipeTimeout, and then click Modify.
5. 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 may find you need increase this number. 300000 (5 minutes) may be more suitable.
6. Restart the computer.
Note: This workaround may resolve the problem where the service does not start.
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.