This was a newly installed SQL Server and after the restart of the server the reporting services failed to start every time when we try to start it. We checked all the areas and found everything fine.
Then we came to know that this is a kind of generic error; the Microsoft Windows Service Control Manager controls the state (i.e., started, stopped, paused, etc.) of all installed Windows services and by default, the Service Control Manager will wait 30,000 milliseconds (30 seconds) for a service to respond but certain configurations, technical restrictions, or performance issues may result in the service taking longer than 30 seconds to start.
Resolution: 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.
- Click Start, click Run, type regedit, and then click OK.
- Locate and then click the following registry subkey:
- In the right pane, locate the ServicesPipeTimeout entry.
Note If the ServicesPipeTimeout entry does not exist, you must create it.
To do this, follow these steps:
On the Edit menu, point to New, and then click DWORD Value.
4. Type ServicesPipeTimeout, and then press ENTER.
5. Right-click ServicesPipeTimeout, and then click Modify.
6. Click Decimal, type 60000\120000, and then click OK.
This value represents the time in milliseconds before a service times out.