The Windows services timeout during boot time after the installation of the ITCM Agent


Article ID: 17466


Updated On:


CA Automation Suite for Data Centers - Configuration Automation CA Client Automation - Asset Management CA Client Automation - IT Client Manager CA Client Automation CA Client Automation - Remote Control CA Client Automation - Asset Intelligence CA Client Automation - Desktop Migration Manager CA Client Automation - Patch Manager CA Server Automation



Errors like the following may be seen after installing the ITCM agent on a server with limited resources (CPU/memory):/p>

Timeout (30000 milliseconds) waiting for the Windows System Resource Manager service to connect./p>

Timeout (30000 milliseconds) waiting for a transaction response from the iphlpsvc service./p>

Timeout (30000 milliseconds) waiting for a transaction response from the LanmanServer service./p>

The Server service failed to start due to the following error:
"Error 1053: The service did not respond to the start or control request in a timely fashion."/p>



CA Client Automation - All Versions


This means that the 'Server' service does not start. So network shares and other functions are broken./p>

If failing services are manually started afterwards, they start up fine


ITCM comes with a number of services that, like many other services, are started automatically at boot time. This means CPU/Memory resources need to be spread amongst more services than before. On system with limited resources, 30 seconds may not be enough for the Server service (or any other service listed in the error message) to start when the system is busy rebooting. To resolve this issue, increase the timeout period for starting up services as follows:

Create the following registry entry:
Subkey: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control
Name: ServicesPipeTimeout
Data: The number of milliseconds that you want services to start before timing out.

To create this registry entry, follow these steps:
-- Click Start, click Run, type regedit, and click OK.
-- Locate and open the following registry subkey:
-- Right-click Control, point to New, and select DWORD Value.
-- In the New Value #1 box, type ServicesPipeTimeout, and then press ENTER.
-- Right-click ServicesPipeTimeout, and click Modify.
-- Click Decimal, type the number of milliseconds that you want the services to boot until the service times out. Click OK.
For example, to wait 60 seconds before the service times out, type 60000.
-- Quit Registry Editor, and then restart the computer.

Additional Information:

IMPORTANT: This article contains information about modifying the registry.
Before you modify the registry, make sure to create back up of the registry and ensure that you understand how to restore the registry if a problem may occur.
For more information about how to back up, restore, and edit the registry, please review the relevant Microsoft Knowledge Base articles on


Release: SEAUBC99000-12.8-Server Automation-Base Configuration