Hi,

I am configuring a new farm for the first time and I am getting a really annoying error with my reporting service.

I am running on Windows server 2012 R2 with a report server on SQL 2014 SP1 Enterprise.

I am running Sharepoint 2013.

I have no issues installing but when I open System Settings in Manage Reporting Services Application - Reporting Service. I get the following error.

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'. ---> Microsoft.ReportingServices.Library.InvalidReportServerDatabaseException: 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'. 

I have updated to the latest service pack and CU2 but I still get this problem. Anyone got any ideas?

Hi,

As I understand, you encountered the error when opening System Settings in Manage Reporting Services Application in SharePoint 2013.

You could check if the application pool account for SSRS has the enough rights to the SharePoint farm.

You could go to report service Configuration and check if the server status is stopped. If the status is stopped, you could start the service.

There are similar cases:

https://social.technet.microsoft.com/Forums/windowsserver/en-US/178874bc-fd65-4d47-a219-64daaba05a27/ssrs-2012-with-sharepoint-2013-scheduled-reports-error?forum=sqlreportingservices

https://social.technet.microsoft.com/Forums/office/en-US/e19bed32-7ca2-4d4a-9dbd-6e7ca64354d1/version-error-at-reporting-services?forum=systemcenter

Best regards,

Sa

My farm is experiencing this error also after the installation of Hotfix 5613 for SQL Server 2012 (KB3045319) on the app servers that run SQL Reporting Service. 

Before the installation Reporting Service was fully functional and Power View sheets rendered with out error.  The above error occurs when attempting to open a Power View sheet in the browser.  It is possible to open the sheet "with Power View" without encountering the error on some Power View sheets - but inconsistent - some sheets still encounter the error.

This is the full text of the error:

<detail><ErrorCode xmlns="rsInvalidReportServerDatabase</ErrorCode><HttpStatus">http://www.microsoft.com/sql/reportingservices">rsInvalidReportServerDatabase</ErrorCode><HttpStatus xmlns="400</HttpStatus><Message">http://www.microsoft.com/sql/reportingservices">400</HttpStatus><Message xmlns="The">http://www.microsoft.com/sql/reportingservices">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'. ---&gt; Microsoft.ReportingServices.Library.InvalidReportServerDatabaseException: 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'.</Message><HelpLink xmlns="http://go.microsoft.com/fwlink/?LinkId=20476&EvtSrc=Microsoft.ReportingServices.Diagnostics.Utilities.ErrorStrings&EvtID=rsInvalidReportServerDatabase&ProdName=Microsoft%20SQL%20Server%20Reporting%20Services&ProdVer=11.0.3321.0</HelpLink><ProductName">http://www.microsoft.com/sql/reportingservices">http://go.microsoft.com/fwlink/?LinkId=20476&amp;EvtSrc=Microsoft.ReportingServices.Diagnostics.Utilities.ErrorStrings&amp;EvtID=rsInvalidReportServerDatabase&amp;ProdName=Microsoft%20SQL%20Server%20Reporting%20Services&amp;ProdVer=11.0.3321.0</HelpLink><ProductName xmlns="Microsoft">http://www.microsoft.com/sql/reportingservices">Microsoft SQL Server Reporting Services</ProductName><ProductVersion xmlns="11.0.3321.0</ProductVersion><ProductLocaleId">http://www.microsoft.com/sql/reportingservices">11.0.3321.0</ProductVersion><ProductLocaleId xmlns="127</ProductLocaleId><OperatingSystem">http://www.microsoft.com/sql/reportingservices">127</ProductLocaleId><OperatingSystem xmlns="OsIndependent</OperatingSystem><CountryLocaleId">http://www.microsoft.com/sql/reportingservices">OsIndependent</OperatingSystem><CountryLocaleId xmlns="1033</CountryLocaleId><MoreInformation">http://www.microsoft.com/sql/reportingservices">1033</CountryLocaleId><MoreInformation xmlns="<Source>ReportingServicesLibrary</Source><Message">http://www.microsoft.com/sql/reportingservices"><Source>ReportingServicesLibrary</Source><Message msrs:ErrorCode="rsInvalidReportServerDatabase" msrs:HelpLink="http://go.microsoft.com/fwlink/?LinkId=20476&amp;EvtSrc=Microsoft.ReportingServices.Diagnostics.Utilities.ErrorStrings&amp;EvtID=rsInvalidReportServerDatabase&amp;ProdName=Microsoft%20SQL%20Server%20Reporting%20Services&amp;ProdVer=11.0.3321.0" xmlns:msrs="The">http://www.microsoft.com/sql/reportingservices">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'.</Message></MoreInformation><Warnings xmlns="http://www.microsoft.com/sql/reportingservices" /></detail>

 update  when resolution is found.

Issue is now resolved.  Problem was incompatible and mismatched versions of SQL builds on the servers running Reporting Service application instances.  Reporting Services was installed on three servers in the farm.  One had SSRS SP2 installed (11.0.5058), the other two were running SP1 + a hotfix (11.0.3321).  When the SQL hotfix was applied to the backend servers where the RS Service App db's reside the database schemas were upgraded to 11.0.5613.0).  At the same time one of the app servers running RS Service Application was upgraded but the other two servers were left at their original build (11.0.3321.0). 

Note too that the RS Add-in is also upgraded by the installation of the Hotfix - control panel programs and features indicates that it's at version 5613.  All others in the farm were at v 3321.

Long and short of the resolution:  Upgrade all RS servers and Add-ins at the same time to matching builds.

Following the completion of the upgrades Reporting server errors ceased and Power View sheets rendered as expected.

Error displayed as follows; now resolved: