23 September 2015

SQL Server Version List

↓ SQL Server 2016
     codename ?
↓ SQL Server 2014
     codename Hekaton SQL14
or 12.1.4100.1
↓ SQL Server 2012
     codename Denali
or 11.1.3000.0
or 11.2.5058.0
↓ SQL Server 2008 R2
     codename Kilimanjaro
or 10.51.2500.0
or 10.52.4000.0
or 10.53.6000.34
↓ SQL Server 2008
     codename Katmai
or 10.1.2531.0
or 10.2.4000.0
or 10.3.5500.0
or 10.4.6000.29
↓ SQL Server 2005
     codename Yukon
↓ SQL Server 2000
     codename Shiloh
↓ SQL Server 7.0
     codename Sphinx

22 September 2015

The version of the report server database is either in a format that is not valid, or it cannot be read.

Problem : 

The version of the report server database is either in a format that is not valid, or it cannot be read. The found version is '163'. The expected version is '162'. (rsInvalidReportServerDatabase)


1. Verify the ReportServer Database compatibility.

2. Change the Compatibility to previous version and restart the services.

3. If the above fails check the RSEXEC role has been granted for the DBO

  1. Open SQL Server Management Studio and connect to the database that hosts the ReportServer and ReportServerTempDB databases.
  2. In Object Explorer, expand the following nodes: Databases, ReportServer, Security, Roles, and Database Roles.
  3. Right-click db_owner, and click Properties.
  4. On the Database Role Properties page, click Add.
  5. On the Select Database User or Role page, type RSExecRole, and then click OK twice.
  6. Repeat these steps with the ReportServerTempDB.
  7. Restart the SSRS Services.

4. If above is already in place then it could be the latest security patch applied on the SQL Server.

5. Verify any CU/Hotfix  which has been applied and caused the issue.

6. Rollback the patch or if its on cluster apply the same patch on the other node too.

Note: Even though SSRS is not a cluster aware component But this security patch will also apply on the SQL Server and makes SSRS to stop working.