InstantForum.NET v2.9.0SQLServerCentralhttp://www.sqlservercentral.com/Forums/notifications@sqlservercentral.comMon, 20 May 2013 19:34:27 GMT20http://www.sqlservercentral.com/Forums/Topic850540-1550-1.aspxthanks for posting this, most useful, especially detailing the steps.I hit this error (on a server restart, not an install) and added the ServicesPipeTimeout DWORD, in my case SSRS then started without the reboot, so worth giving it a try before the reboot if you hit this.Don't think it was a load issue because no-one was connected to the server at all at the time.another URL on this [url=http://www.nixadmins.net/2012/08/22/sql-server-reporting-services-service-fails-to-start/]here[/url]Sun, 11 Nov 2012 13:09:41 GMTgeorge sibbaldhttp://www.sqlservercentral.com/Forums/Topic850540-1550-1.aspxthat's an interesting one for sure.Thu, 21 Jan 2010 06:50:01 GMTcolin.Leversuch-Robertshttp://www.sqlservercentral.com/Forums/Topic850540-1550-1.aspxI wanted to post this so it would be out there on the Web for anyone else searching for a solution to this problem.I've got a Windows 2008 box and I'm installing SQL 2008 on it. I was also installing SSRS as well as other components.When the install completed it had failed, and the only Item that failed was SSRS. I combed the logs and could not find an error, as a matter of fact the logs indicated it had installed successfully and the only error in the event logs was as followsA timeout was reached (30000 milliseconds) while waiting for the SQL Server Reporting Services (MSSQLSERVER) service to connect.Event ID 7009I found a post on the forum here for SQL 2005 SSRS, [url=http://www.sqlservercentral.com/Forums/Topic470451-146-1.aspx]http://www.sqlservercentral.com/Forums/Topic470451-146-1.aspx[/url] , which led to this MS article, [url=http://support.microsoft.com/?kbid=884495]http://support.microsoft.com/?kbid=884495[/url], and it fixed my install.Here are the steps so you don't have to click on the links 1. Click Start, click Run, type regedit, and then click OK.2. Locate and then click the following registry subkey: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control3. Right-click Control, point to New, and then click DWORD Value.4. In the New Value #1 box, type ServicesPipeTimeout, and then press ENTER.5. Right-click ServicesPipeTimeout, and then click Modify.6. Click Decimal, type the number of milliseconds that you want to wait until the service times out, and then click OK.For example, to wait 60 seconds before the service times out, type 60000.Quit Registry Editor, and then restart the computer.I changed mine to 120000, and upon reload bam it was up and running.Wed, 20 Jan 2010 08:33:45 GMTSQLBalls