Remote installation failed with error: Cannot connect to SCM error code 1053

  • KM03773328
  • 27-Jan-2021
  • 27-Jan-2021

Archived Content: This information is no longer maintained and is provided "as is" for your convenience.


Issue happened on the system with unstable network


Remote installation got following error:
Cannot connect to SCM error code 1053 (The service could not start on a timely fashion)


We do a further investigation and found out that the connection between Cell Manager and this client is extremely slow
Data Protector install service was timed-out due to the slowness of the network
It couldn't start install service on time


1- Examine the network connectivity speed and fix from network end if possible
2- I do research and found out one registry setting can help to increase the timeout to start service: ServicesPipeTimeout

Go to Start > Run > and type regedit
Navigate to: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control
With the control folder selected, right click in the pane on the right and select new DWORD Value
Name the new DWORD: ServicesPipeTimeout
Right-click ServicesPipeTimeout, and then click Modify
Click Decimal, type '180000', and then click OK
Restart the computer
The Microsoft Windows Service Control Manager controls the state (i.e., started, stopped, paused, etc.) of all installed Windows services. By default, the Service Control Manager will wait 30,000 milliseconds (30 seconds) for a service to respond. However, certain configurations, technical restrictions, or performance issues may result in the service taking longer than 30 seconds to start and report ready to the Service Control Manager.
By editing or creating the ServicesPipeTimeout DWORD value, the Service Control Manager timeout period can be overridden, thereby giving the service more time to start up and report ready to the Service.
3- If problem still persists, I think you have no choice but upgrade these problematic clients LOCALLY.