Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

Report Services Fails to Start, and fails installation Expand / Collapse
Author
Message
Posted Wednesday, January 20, 2010 8:33 AM


Old Hand

Old HandOld HandOld HandOld HandOld HandOld HandOld HandOld Hand

Group: General Forum Members
Last Login: Tuesday, February 25, 2014 2:26 PM
Points: 386, Visits: 626
I 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 follows

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

Event ID 7009

I found a post on the forum here for SQL 2005 SSRS, http://www.sqlservercentral.com/Forums/Topic470451-146-1.aspx , which led to this MS article, http://support.microsoft.com/?kbid=884495, 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\Control
3. 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.



Twitter: @SQLBalls
Blog: http://www.SQLBalls.com
Post #850540
Posted Thursday, January 21, 2010 6:50 AM
SSCrazy

SSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazy

Group: General Forum Members
Last Login: Monday, June 9, 2014 6:02 AM
Points: 2,674, Visits: 697
that's an interesting one for sure.

The GrumpyOldDBA
www.grumpyolddba.co.uk
http://sqlblogcasts.com/blogs/grumpyolddba/
Post #851211
Posted Sunday, November 11, 2012 1:09 PM
SSCertifiable

SSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiable

Group: General Forum Members
Last Login: 2 days ago @ 3:40 AM
Points: 5,989, Visits: 12,925
thanks 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 here


---------------------------------------------------------------------

Post #1383462
Posted Friday, December 27, 2013 11:05 AM


SSC Veteran

SSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC Veteran

Group: General Forum Members
Last Login: Thursday, August 28, 2014 7:35 AM
Points: 269, Visits: 778
Thanks for posting this.

I just configured a new server with SQL Server services. For some reason, SSRS would not start.

I used these steps and rebooted. The service started automatically.

Thanks for posting such detail. That saved me a lot of troubleshooting time.



Tony



Post #1526231
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse