Help! I'm panicking a bit here ... I got a call at home today on a Sunday when one of the system admins at work apparently applied some Windows updates (possibly including SQL Server SP2 -- I thought it was installed already, but I see an error in the event log during it's installation, and when I tried to manually install it, some of the related components appeared to be still pre-SP2) ...
EVERYTHING else is up, and working fine -- database server, analysis server, etc. However, the primary function of this server is to serve crucial daily reports for an internal group, and now the Reporting Services stuff won't restart at all. No matter what I try, I just get a variation of this:
From the Reporting Services Configuration Manager:
The best hint I got was a message which claims an Error in timer Running Requests DB : Microsoft.ReportingServices.Diagnostics.Utilities.ReportServerDatabaseUnavailableException: The report server cannot open a connection to the report server database. A connection to the database is required for all requests and processing. ---> Microsoft.ReportingServices.Diagnostics.Utilities.ReportServerServiceUnavailableException: The Report Server Windows service 'ReportServer' is not running. The service must be running to use Report Server....
However, the database is running, and the user account is correct, and the Reporting Services Configuration Manger shows green checkmarks on everything except the Server Status and the Initialization (which obviously fail because the service won't start!) (oh, and SharePoint Integration and Encryption Keys, which remain unset).
EVERYTHING else is up, and working fine -- database server, analysis server, etc. However, the primary function of this server is to serve crucial daily reports for an internal group, and now the Reporting Services stuff won't restart at all. No matter what I try, I just get a variation of this:
From the Reporting Services Configuration Manager:
System.InvalidOperationException: Cannot start service ReportServer on computer 'PRODB'. ---> System.ComponentModel.Win32Exception: The service did not respond to the start or control request in a timely fashion
--- End of inner exception stack trace ---
at System.ServiceProcess.ServiceController.Start(String[] args)
at System.ServiceProcess.ServiceController.Start()
at ReportServicesConfigUI.Panels.ServerInformationPanel.StartStopServiceTask(Boolean start)
From the Event Viewer System log:--- End of inner exception stack trace ---
at System.ServiceProcess.ServiceController.Start(String[] args)
at System.ServiceProcess.ServiceController.Start()
at ReportServicesConfigUI.Panels.ServerInformationPanel.StartStopServiceTask(Boolean start)
Event Type: Error
Event Source: Service Control Manager
Event Category: None
Event ID: 7009
Date: 7/27/2008
Time: 7:26:24 PM
User: N/A
Computer: PRODB
Description:
Timeout (30000 milliseconds) waiting for the SQL Server Reporting Services (MSSQLSERVER) service to connect.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Event Type: Error
Event Source: Service Control Manager
Event Category: None
Event ID: 7000
Date: 7/27/2008
Time: 7:26:24 PM
User: N/A
Computer: PRODB
Description:
The SQL Server Reporting Services (MSSQLSERVER) service failed to start due to the following error:
The service did not respond to the start or control request in a timely fashion.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
The Reporting Services logs mostly just repeat that "The Report Server Windows service 'ReportServer' is not running." ...Event Source: Service Control Manager
Event Category: None
Event ID: 7009
Date: 7/27/2008
Time: 7:26:24 PM
User: N/A
Computer: PRODB
Description:
Timeout (30000 milliseconds) waiting for the SQL Server Reporting Services (MSSQLSERVER) service to connect.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Event Type: Error
Event Source: Service Control Manager
Event Category: None
Event ID: 7000
Date: 7/27/2008
Time: 7:26:24 PM
User: N/A
Computer: PRODB
Description:
The SQL Server Reporting Services (MSSQLSERVER) service failed to start due to the following error:
The service did not respond to the start or control request in a timely fashion.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
The best hint I got was a message which claims an Error in timer Running Requests DB : Microsoft.ReportingServices.Diagnostics.Utilities.ReportServerDatabaseUnavailableException: The report server cannot open a connection to the report server database. A connection to the database is required for all requests and processing. ---> Microsoft.ReportingServices.Diagnostics.Utilities.ReportServerServiceUnavailableException: The Report Server Windows service 'ReportServer' is not running. The service must be running to use Report Server....
However, the database is running, and the user account is correct, and the Reporting Services Configuration Manger shows green checkmarks on everything except the Server Status and the Initialization (which obviously fail because the service won't start!) (oh, and SharePoint Integration and Encryption Keys, which remain unset).