Skip to content

SSRS service status is Change Pending

Ever seen SQL Server Reporting Services service is not getting started on time and the service status is Change Pending? Why SSRS service is not starting and stuck at Change Pending? Here we will talk about this issue, its possible cause and resolution.

Problem and possible issue

SQL Server Reporting Service is not getting started or taking too long to start and the service status is ‘Change Pending’

Mostly you will hit this issue after server reboot and when all the SQL Server services tries to start. Now for SSRS to start successfully, it needs ReportServer database to be online, but when SSRS tries to start it didn’t find this database online and got stuck at Change Pending. Status will move to started only when ReportServer database comes online.

Reason why this database didn’t get started on time may be because of resource issue on the server. If you hit issue more frequently, then you may have to think for hardware upgrade (run perfmon to do more analysis on server performance).

Analyzing Error Message

You will find below errors (may be multiple times) in the current log file of SSRS error logs located at ..\MSRS10_50.SQL2008R2\Reporting Services\LogFiles (.. is the base drive and/or directory path where SSRS is installed):-

library!DefaultDomain!448!09/29/2011-22:36:16:: e ERROR: Throwing Microsoft.ReportingServices.Library.ReportServerDatabaseUnavailableException: , Microsoft.ReportingServices.Library.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. —> System.Data.SqlClient.SqlException: Cannot open database “ReportServer$SQL2008R2” requested by the login. The login failed.

Login failed for user ‘MACHINE23AF\SQLServer’.

library!WindowsService_0!448!09/29/2011-22:36:19:: e ERROR: Throwing Microsoft.ReportingServices.Library.ReportServerDatabaseUnavailableException: , Microsoft.ReportingServices.Library.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. —> System.Data.SqlClient.SqlException: Cannot open database “ReportServer$SQL2008R2” requested by the login. The login failed.

Login failed for user ‘MACHINE23AF\SQLServer’.

Now if you analyze the SQL Server error log and tries to map it with SSRS errors log. You will find below entries around the time when errors are written in SSRS logs around same time:-

2011-09-29 22:36:12.09 Logon       Error: 18456, Severity: 14, State: 38.

2011-09-29 22:36:12.09 Logon       Login failed for user ‘MACHINE23AF\SQLServer’. Reason: Failed to open the explicitly specified database. [CLIENT: <local machine>]

2011-09-29 22:36:12.21 spid13s     Service Broker manager has started.

2011-09-29 22:36:19.48 Logon       Error: 18456, Severity: 14, State: 38.

2011-09-29 22:36:19.48 Logon       Login failed for user ‘MACHINE23AF\SQLServer’. Reason: Failed to open the explicitly specified database. [CLIENT: <local machine>]

2011-09-29 22:36:25.21 Logon       Error: 18456, Severity: 14, State: 38.

2011-09-29 22:36:25.21 Logon       Login failed for user ‘MACHINE23AF\SQLServer’. Reason: Failed to open the explicitly specified database. [CLIENT: <local machine>]

2011-09-29 22:36:35.23 Logon       Error: 18456, Severity: 14, State: 38.

2011-09-29 22:36:35.23 Logon       Login failed for user ‘MACHINE23AF\SQLServer’. Reason: Failed to open the explicitly specified database. [CLIENT: <local machine>]

2011-09-29 22:36:42.18 spid18s     Starting up database ‘ReportServer$SQL2008R2’.

2011-09-29 22:36:42.19 spid17s     Starting up database ‘msdb’.

2011-09-29 22:36:42.19 spid20s     Starting up database ‘ReportServer$SQL2008R2TempDB’.

2011-09-29 22:36:42.59 spid6s      Recovery is writing a checkpoint in database ‘ReportServer$SQL2008R2TempDB’ (6). This is an informational message only. No user action is required.

2011-09-29 22:36:43.75 spid6s      Recovery completed for database ReportServer$SQL2008R2 (database ID 5) in 1 second(s) (analysis 40 ms, redo 21 ms, undo 587 ms.) This is an informational message only. No user action is required.