The No Custom Security Extensions rule failure stopped a SQL Server upgrade because Reporting Services had custom extensions configured. The fix that worked was to clear the extensions in RSReportServer.config, upgrade, and put them back afterward.
Setup Error 1060: The Specified Service Does Not Exist During Upgrade
Setup error 1060 stopped an in-place upgrade from SQL Server 2008 R2 to 2014 right after the product key. The setup log asked for a ReportServer service that no longer existed. Removing the leftover SSRS fixed it.
SQL SERVER – Reporting Services Not Starting After Maintenance Window
Reporting Services not starting after maintenance? On my lab server every SQL service came back except SSRS. Here is what the log showed.
SQL SERVER – Install Error – The Reporting Services Catalog Database File Exists. Select a Reporting Services files-only mode installation
A remote command-line install of SQL Server failed with: The Reporting Services catalog database file exists. Here is how I helped my client fix it.
SQL SERVER – The Report Server Cannot Open a Connection to the Report Server Database. (rsReportServerDatabaseLogonFailed)
A report viewer failed with rsReportServerDatabaseLogonFailed: the report server cannot open a connection to the report server database. Here is the fix.
SQL SERVER – Event ID 107- Report Server Windows Service (MSSQLSERVER) cannot connect to the report server database.
Event ID 107 says the Report Server Windows service cannot connect to the report server database. Here is how I fixed it.
Moving SSRS Reports to a New Server
Moving SSRS reports to a new server requires the ReportServer databases, encryption key, data source checks, and subscription rehearsal.