Error 1053 : "The service did not respond to start or control request in a timely fashion" while starting the Application Server Service in Control Compliance Suite 10.x
When a service starts, the service communicates to the Service Control Manager how long the service must have to start (the timeout period for the service). If the Service Control Manager does not receive a "service started" notice from the service within this timeout period, the Service Control Manager terminates the process that hosts the service. This timeout period is typically less than 30 seconds.
Perform the following steps on the Control Compliance Suite 10.5.1 Application Server computer
Warning: Incorrect use of the Windows registry editor may prevent the operating system from functioning properly. Great care should be taken when making changes to a Windows registry. Registry modifications should only be carried-out by persons experienced in the use of the registry editor application. It is recommended that a complete backup of the registry and workstation be made before making any registry changes.
- Click Start > Run, then type regedit
- Locate, and then right-click the following registry subkey: KEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control
- Point to New, and then click DWORD Value. In the right pane of Registry Editor, notice that New Value #1 (the name of a new registry entry) is selected for editing.
- Type ServicesPipeTimeout to replace New Value #1, and then press enter.
- Right-click the ServicesPipeTimeout registry entry that you created in step 3, and then click Modify. The Edit DWORD Value dialog box appears.
- In the Value data text box, type 86400000, and then click OK ( It is the timeout period (in milliseconds) that you want to set for the service. Setting timeout period to 86400000 will set it to 24 hours (86400000 milliseconds)
- Restart the computer.