Today I was working on a demo-environment on my laptop, which has been running Windows 8 since last week. As a side note, I love the Hyper-V role but it does not seem to perform as well as on a server OS or even VMWare Workstation. I draw the conclusion since services in my VM’s fail to start due to timeout, as the case was today with the SQL Server Reporting service service.
So trying to start SRS the eventlog shows A timeout was reached (30000 milliseconds) while waiting for the SQL Server Reporting Services (MSSQLSERVER) service to connect. I noticed a performance issue earlier while installing SP1 and CU6 on the SQL server so I was guessing the timeout value was to low.
Changing the timeout value does not degrade the performance of the server so I decided it was worth a try, fire up Regedit.exe and move to HKLM\System\CurrentControllset\Control in the right window you should see the value ServicesPipeTimeout, if it isn’t there just create a new DWORD value, name it ServicesPipeTimeout and add a decimal value higher than 30 000. I went with 120 000.
After that I rebooted the server and sure enough the SRS service was able to start.
No related posts.
[...] SQL Server Reporting Services service fails to start « Nixadmins.net. This entry was posted in Uncategorized by Jason Deary. Bookmark the permalink. [...]
Great! Helped me out, didn’t remember the regedit key to modify. Did you still encounter the problem after this change?
Hi Jpinto, no problems after that, as I said this was a lab so it’s been wiped ages ago. Hope you don’t experience the same issues in your production environment.