SQL Server Reporting Services not automatically starting after a reboot

I am surprised how often I get this alert from SCOM – “The Windows service for the Reporting Services instance MSSQLSERVER has stopped on computer XYZ”.

I have seen this more than a couple of times and thought it worth blogging about.

Check the Windows Event Logs (System) and look for “Service Control Manager” failures around the last reboot time with the error message “The SQL Server Reporting Services (MSSQLSERVER) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion”. There is usually a second failure nearby : “A timeout was reached (30000 milliseconds) while waiting for the SQL Server Reporting Services (MSSQLSERVER) service to connect.”

The solution is to increase the default service time-out as follows :

  • Open Regedit
  • Navigate to: KEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control
  • Create a new DWORD value called ServicesPipeTimeout
  • Modify it and ensure it is set to Decimal  and enter the value 60000
  • Close Regedit
  • Reboot the server
  • Confirm that SQL Reporting services satrted correctly

Be aware that this affects all windows services and not just Reporting Services. For safety, backup the registry before applying any changes.

%d bloggers like this: