If you are using SQL 2008 R2 SP2 as a database instance for ConfigMgr12, you may face some weird issues regarding SQL Reporting Services.
Very first thing you may face after you update current SQL Server 2008 R2 to Service Pack 2 is timeout problem.
By default SQL will try to start reporting services within 30 seconds which is default timeout value. Therefore if you restart your SQL Server you may see that service did not start with following error:
A timeout was reached (30000 milliseconds) while waiting for the SQL Server Reporting Services (MSSQLSERVER) service to connect
To overcome above timeout problem you can create following Regedit key to increase timeout value:
Decimal : 120000
That will increase default timeout value to 120 seconds. After you restart service, it will start automatically.
But this regedit hack does not solve CM12 Reporting Services Role Installation problem.
If you start Reporting Services point role installation on SQL Server within ConfigMgr12 console, it will create a root reporting folder, create CM12 related reports and then restart Reporting Services.
That’s where problem starts. CM12 will not use configured timeout value and will try to restart service within 1 min. And if your SQL Server starts SRS service in more than 1 min, Reporting Services Role installation will fail. Here is the log file from srsp.log file.
Starting service 'ReportServer'
Time out has expired and the operation has not been completed
To solve this problem easily, you need to install Cumulative Update 1 for Configuration Manager 2012.
- A Reporting Services Point may not be installed or start if the SQL Reporting Service does not start within one minute. The srssp.log file may contain entries that resemble the following entry:Starting service 'ReportServer'
Time out has expired and the operation has not been completed.