SQL Server 2008 Reporting Services Hang on Startup
-
Every time I start the Windows 2003 server after installing SQL Server 2008, I get an error upon start up.
Event Type:Information
Event Source:Application Popup
Event Category:None
Event ID:26
Date:6/12/2009
Time:9:57:47 AM
User:N/A
Computer:USDPITBHR1MS104
Description:
Application popup: Service Control Manager : At least one service or driver failed during system startup. Use Event Viewer to examine the event log for details.
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:7022
Date:6/12/2009
Time:9:57:59 AM
User:N/A
Computer:USDPITBHR1MS104
Description:
The SQL Server Reporting Services (MSSQLSERVER) service hung on starting.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Reporting Service Eventually Starts, but this dialog is annoying every time you start the server. Does anyone know how to fix this? I will be patiently waiting for a response. :Whistling:
-
Is there any additional information in the Event Log? You may be able to see which service or driver is failing. The event log should provide additional detail about why that particular service or driver failed too.
Application popup: Service Control Manager : At least one service or driver failed during system startup. Use Event Viewer to examine the event log for details.
There might be a service that Reporting Services (SSRS) is dependant upon, but it has invalid credentials or is disabled. Always check the simple things first, before you start over-thinking a solution. 😛
Has this error only recently started too, or has SSRS always started this way?
-
Note that Reporting Services do eventually start and connect, I am just trying to see if there is a way to get rid of the error message on boot up.
Here is some additional info from the logs.
Event Type:Failure Audit
Event Source:MSSQLSERVER
Event Category:Logon
Event ID:18456
Date:6/17/2009
Time:7:38:57 AM
User:NT AUTHORITY\NETWORK SERVICE
Computer:USDPITBHR1MS104
Description:
Login failed for user 'NT AUTHORITY\NETWORK SERVICE'. Reason: Failed to open the explicitly specified database. [CLIENT: ]
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 18 48 00 00 0e 00 00 00 .H......
0008: 10 00 00 00 55 00 53 00 ....U.S.
0010: 44 00 50 00 49 00 54 00 D.P.I.T.
0018: 42 00 48 00 52 00 31 00 B.H.R.1.
0020: 4d 00 53 00 31 00 30 00 M.S.1.0.
0028: 34 00 00 00 07 00 00 00 4.......
0030: 6d 00 61 00 73 00 74 00 m.a.s.t.
0038: 65 00 72 00 00 00 e.r...
Event Type:Error
Event Source:Report Server Windows Service (MSSQLSERVER)
Event Category:Management
Event ID:107
Date:6/17/2009
Time:7:38:52 AM
User:N/A
Computer:USDPITBHR1MS104
Description:
Report Server Windows Service (MSSQLSERVER) cannot connect to the report server database.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
-
I'm guessing that you're unable to run any reports too. It appears that the 'NT AUTHORITY\NETWORK SERVICE' account is the account that you have SSRS associated with.
It sounds like the problem is that the SSRS service is starting and running without a problem. I think the issue is being caused by one of these:
1. The service doesn't have permission to access the ReportingServices database.
2. The database used by SSRS doesn't exist.
3. Your SSRS is configured for an incorrect or nonexistent database.
Login failed for user 'NT AUTHORITY\NETWORK SERVICE'. Reason: Failed to open the explicitly specified database. [CLIENT: ]
...
Report Server Windows Service (MSSQLSERVER) cannot connect to the report server database.
NOTE: I'm using SQL Server 2008 Enterprise Edition SP1, so your steps might be slightly different but overall this should provide you with a foundational understanding of what needs to be done.
Here's what I recommend:
1. Check your SSRS settings by opening the Reporting Services Configuration tool - Start Menu\Programs\Microsoft SQL Server 2008\Configuration Tools
2. Connect to your SSRS instance.
3. Click the Database tab and check the Database name: value. This will tell you the name (if any) of the database SSRS is configured to use for it's own stuff.
4. Open your SQL Server Management Studio (SSMS), connect to your instance and look for the database you found from step 3.
You should see the report database and a database with 'TempDB' at the end also. On my server, I have 'ReportServer' & 'ReportServerTempDB'.
5. If you have the 'ReportServer' database (or the database listed in step 3), but your had a different database listed on step 1, then go back to the Reporting Services Configuration tool > Database tab and click the Change Database button.
6. This will open a wizard that will walk you through the steps to either create a new database if one doesn't exist, or reconfigure SSRS to use an existing database. The wizard isn't too complicated, but if you need help, just post back to this topic.
7. If this still doesn't solve your problem, I'd guess that the 'NT AUTHORITY\NETWORK SERVICE' account doesn't have sufficient access to the database found in step 3. Try giving the account permission to the database within the security settings.
-
Thanks for your reply. The issue I am seeing happened right after SQL 2008 and Reporting Services was set up. I checked all of the things you mentioned above, and the database seems OK. It appears to be a timing thing because Reporting services eventually starts up and I can get to the Reporting Services Home page. I did notice some errors in the Application log and a Failure Audit that mention the 'NT AUTHORITY\NETWORK SERVICE' (see below)
Event ID 17187
Event Type:Error
Event Source:MSSQLSERVER
Event Category:Logon
Event ID:17187
Date:6/18/2009
Time:6:43:23 AM
User:N/A
Computer:USDPITBHR1MS104
Description:
SQL Server is not ready to accept new client connections. Wait a few minutes before trying again. If you have access to the error log, look for the informational message that indicates that SQL Server is ready before trying to connect again. [CLIENT: 149.59.133.231]
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 23 43 00 00 10 00 00 00 #C......
0008: 10 00 00 00 55 00 53 00 ....U.S.
0010: 44 00 50 00 49 00 54 00 D.P.I.T.
0018: 42 00 48 00 52 00 31 00 B.H.R.1.
0020: 4d 00 53 00 31 00 30 00 M.S.1.0.
0028: 34 00 00 00 00 00 00 00 4.......
Event ID 107
Event Type:Error
Event Source:Report Server Windows Service (MSSQLSERVER)
Event Category:Management
Event ID:107
Date:6/18/2009
Time:6:43:23 AM
User:N/A
Computer:USDPITBHR1MS104
Description:
Report Server Windows Service (MSSQLSERVER) cannot connect to the report server database.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Event ID 18456
Event Type:Failure Audit
Event Source:MSSQLSERVER
Event Category:Logon
Event ID:18456
Date:6/18/2009
Time:6:43:24 AM
User:NT AUTHORITY\NETWORK SERVICE
Computer:USDPITBHR1MS104
Description:
Login failed for user 'NT AUTHORITY\NETWORK SERVICE'. Reason: Failed to open the explicitly specified database. [CLIENT: ]
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 18 48 00 00 0e 00 00 00 .H......
0008: 10 00 00 00 55 00 53 00 ....U.S.
0010: 44 00 50 00 49 00 54 00 D.P.I.T.
0018: 42 00 48 00 52 00 31 00 B.H.R.1.
0020: 4d 00 53 00 31 00 30 00 M.S.1.0.
0028: 34 00 00 00 07 00 00 00 4.......
0030: 6d 00 61 00 73 00 74 00 m.a.s.t.
0038: 65 00 72 00 00 00 e.r...
It's just that every time I reboot, I get the message 'At least one service or driver failed during system startup.' and I have to click OK, and that message is related to Reporting Services.
I found this link-maybe this is a bug.
https://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=377627
I also tried changing the timing as per the information in this link: http://www.sql-server-performance.com/faq/ssrs_server_failing_to_start_p1.aspx (This did not help.)
-
When you're starting SSRS, is your MSSQLSERVER SQL Server service already running?
It sounds like the database service is having to be started when you're starting SSRS and it's taking a while for the SQL Server service to start. I think that SSRS is starting, the SQL Server service is starting, but before the SQL Server service is finished starting, SSRS is displaying the error.
That would explain why you can still connect to the database(s) within SSRS.
-
OK, so here is what we have determined.
If I set SSRS to start manually instead of automatically, then I do not get the error message every time I reboot the computer. So the error message occurs when SSRS is set to start automatically.
If I do not want to see the error message, I need to set SSRS to start manually and then when I want to use Reporting Services I have to Start the service.
I had no luck with the suggestions to increase the time-out value for service startup process at this link: (I set the ServicesPipeTimeout to 120,000).
Thanks again for your quick response! Unless someone can provide me with the magical number to set the ServicesPipeTimeout to, I guess I can't complain if the SSRS runs.
-
One last thing you should check is to make sure that the services I've outlined in red below are set to Automatic. The two non-SSRS services should be running whenever you're trying to run SSRS.
-
This is incredibly annoying - this type of alert makes people think something is wrong with your server. Here's how I worked around the problem:
- Change the startup type for reporting services from "Automatic" to "Manual"
- create a scheduled task:
c:\windows\system32\/net.exe start "SQL Reporting Services (MSSQLSERVER)"- set the scheduled task to run at system startup.
The scheduled task starts later... by the time the service is launched, the SQL server database is up.
None of the other solutions I read about worked.
-
If you're SQL Server is running on Windows Server 2008 or Server 2008 R2, you also have the option of configuring services to start "Automatically (Delayed Start)". This should effectively do the same thing, without having to add a scheduled task.
If you're not using Windows Server 2008, you can also follow this Microsoft Support article:
Microsoft Support: How to delay loading of specific services (http://support.microsoft.com/kb/193888)
-
I'm having the same issue since adding SQL 2008 to this SBS2003 server last month.
I looked at the ReportServer service dependencies; there aren't any!
Alexander's reference to MS KB193888 is the answer.
I've added the following registry setting to the service to make it wait for MSSQLSERVER:
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\ReportServer]
"DependOnService"=hex(7):4d,00,53,00,53,00,51,00,4c,00,53,00,45,00,52,00,56,00, 45,00,52,00,00,00,00,00
In regedit, add a new "Multi-String Value" named "DependOnService" with the value MSSQLSERVER
I haven't tested this yet but I have every confidence it will fix it.
Viewing 11 posts - 1 through 10 (of 10 total)
You must be logged in to reply to this topic. Login to reply