Issue

• When trying to start any Snow service you may receive the error message mentioned in the title: "Error 1053 - The service did not respond in a timely fashion when attempting to start the service"

Environment

• All Snow products
   

Resolution

Potential solution 1 - Increase time-out period

• 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. This time-out period is typically less than 30 seconds. If you do not adjust this time-out period, the Service Control Manager ends the process.
• To adjust this time-out period, follow these steps:

IMPORTANT: Incorrect use of the Microsoft Windows Registry Editor may cause serious problems with your computer, up to and including general operating system corruption and inability to boot. Registry editing should only be performed by those who are sufficiently experienced in the use of the registry editor application.

• 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

If this does not help, the root cause could be an underlying issue with the service. In this case the time out is just a side effect and the tweak will not help as the service cannot start due to this issue (even with more time).
In this case the service should be investigate further (logs) to identify the actual root cause (which is not a time out).

Potential solution 2 - Enable TCP/IP connection

• TCP / IP connections may be disabled by default on your SQL Service. 
• In some instances a solution may be to enable TCP / IP Connection for the SQL Server:
• Open SQL Server Configuration Manager => SQL Server Network Configuration => Protocols for MSSQLSERVER => TCP / IP Enabled
• Enable this with the 32 and 64 bit network Configuration