Regresar
-
Título
Receive error "The service did not respond to the start or control request in a timely fashion (1053)" when trying to install agent remotely -
Descripción
When trying to install the agent from the Deployment page in the Client, the following error "The service did not respond to the start or control request in a timely fashion (1053)" is received. -
Causa
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.
Latency in the network may be delaying the windows service startup, as the windows service start timeout value by default is 30 seconds.
-
Resolución
WORKAROUND 1:
Manually install the Agent on the impacted servers by following the steps in Knowledge Article 138889:
How to manually install the Change Auditor Agent on a remote serverhttps://support.quest.com/change-auditor/kb/138889WORKAROUND 2:Adjust the time-out period for the service to start.To adjust this time-out period, follow these steps:- In Registry Editor, locate, and then right-click the following registry subkey:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control- Point to New, and then click DWORD Value.
- Type ServicesPipeTimeout to replace 'New Value #1', and then press ENTER.
- Right-click the ServicesPipeTimeout registry entry that you created in step c, and then click Modify. The Edit DWORD Value dialog box appears.
- In the Value data text box, type 60000 which equals 60 seconds, and then click OK
- Restart the computer. You must restart the computer for Service Control Manager to apply this change.
- Now retry to push the Agent from the Deployment page.
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.