Sign in with Microsoft
Sign in or create an account.
Select a different account.
You have multiple accounts
Choose the account you want to sign in with.


When you upgrade Microsoft SQL Server Reporting Services instance from Microsoft SQL Server 2012 Service Pack 2 (SP2) Cumulative Update 12 (CU12) or later versions to SQL Server 2012 Service Pack 3 (SP3) or SQL Server 2014, you may receive an error message that resembles the following:

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 ‘164’. The expected version is ‘162’. (rsInvalidReportServerDatabase).


This issue occurs because of a change is made in SQL Server 2012 SP2 CU12 that results in a new ReportServer database version. Because this fix is made after the SQL Server 2014 release, if your SQL Server 2012 SP2 server is on CU12 or a later version, it will have a higher database version than what SQL Server 2014 RTM expects.


Update information

This issue was fixed in the following cumulative updates for SQL Server:

Note SQL Server 2014 RTM version has no more planned CUs so you have to upgrade to either SP1 or SP2 and the corresponding CU to get the fix.

Or, you can upgrade to any build of SQL Server Reporting Services 2016. After you apply the fix, the Reporting Services instance can recognize the new database version correctly.

Hotfix update package information

Restart information

You may have to restart the computer after you apply this hotfix update.

Registry information

To use one of the hotfixes in this package, you don't have to make any changes to the registry.

Need more help?

Want more options?

Explore subscription benefits, browse training courses, learn how to secure your device, and more.

Communities help you ask and answer questions, give feedback, and hear from experts with rich knowledge.

Was this information helpful?

What affected your experience?
By pressing submit, your feedback will be used to improve Microsoft products and services. Your IT admin will be able to collect this data. Privacy Statement.

Thank you for your feedback!