After upgrading to Snow Inventory 25.1 you see Error 1053 - The service did not respond in a timely fashion when attempting to start a Snow product service timeout
After upgrading to Snow Inventory 25.1, a Snow service may fail to start and Windows may display the following error:
Error 1053: The service did not respond to the start or control request in a timely fashion.This error can occur when the service requires more time to start. It can also indicate an underlying service, server performance, or database connectivity issue. This article describes two potential solutions.
Solution 1: Increase the Windows service startup timeout
Windows allows services a limited amount of time to start before reporting them as unresponsive. Increasing the ServicesPipeTimeout registry value gives services more time to initialize.
This setting applies to all Windows services, not only Snow services. A full server restart is required before the change takes effect.
CAUTION: Incorrectly modifying the Windows registry can cause serious operating system problems, including preventing the server from starting. Only someone experienced with Registry Editor should perform these steps.
- Open Start > Run.
- Enter
regedit, and then select OK. - Navigate to:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control- With the Control folder selected, right-click the right pane and select New > DWORD Value.
- Name the value
ServicesPipeTimeout. - Right-click
ServicesPipeTimeout, and then select Modify. - Select Decimal, enter
180000, and then select OK. - Restart the server.
The value 180000 increases the timeout to 180 seconds.
Alternatively, run the following command from an elevated Command Prompt:
reg add "HKLM\SYSTEM\CurrentControlSet\Control" /v ServicesPipeTimeout /t REG_DWORD /d 180000 /fIf the service still does not start, review the Snow logs and Windows Event Logs. Increasing the timeout will not resolve an underlying service failure or server performance issue.
Solution 2: Increase the Windows service startup timeout
TCP/IP connections may be disabled by default on your SQL server. Enabling TCP/IP can help in certain cases.
- Open SQL Server Configuration Manager.
- Go to SQL Server Network Configuration > Protocols for MSSQLSERVER.
- Enable TCP/IP for both 32-bit and 64-bit network configurations.
After applying the relevant solution, start the affected Snow service again. If Error 1053 persists, review the Snow logs and Windows Event Logs to identify the underlying startup failure.
