Technical FAQs

Ask a Question

SQL Reporting Services service will not start

Goals and Symptoms

SQL Server Reporting Services fails to start with the following error:

The SQL Server Reporting Services (ION) service failed to start due to the following error:
The service did not respond to the start or control request in a timely fashion.

Additional errors in the Windows System Log include the following:

A timeout was reached (30000 milliseconds) while waiting for the SQL Server Reporting Services (ION) service to connect.

Facts and Changes


ION Enterprise (IONE) or StruxureWare Power Monitoring (SPM) with SQL Reporting Services

Causes and Fixes


If there are no other errors in the Windows Application or System Logs, the issue might simply be that Reporting Services is taking longer than the 30,000 milliseconds to start up, and the Service Controller is stopping the process.


A simple registry key can be added to increase this timeout.

Important: This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs.

1) Open up regedit.exe and browse to HKLM\System\CurrentControllset\Control
2) If it is not already there, create a new DWORD called ServicesPipeTimeout.
3) Set the value (decimal) to something higher than 30,000 ms (i.e. 120,000 ).
4) Restart the Server and see if the SQL Reporting Services service starts up.

If the service does not start, the timeout might have to be further increased.

Was this helpful?
What can we do to improve the information ?