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)
Solution:
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
- Open SQL Server Management Studio and connect to the database that hosts the ReportServer and ReportServerTempDB databases.
- In Object Explorer, expand the following nodes: Databases, ReportServer, Security, Roles, and Database Roles.
- Right-click db_owner, and click Properties.
- On the Database Role Properties page, click Add.
- On the Select Database User or Role page, type RSExecRole, and then click OK twice.
- Repeat these steps with the ReportServerTempDB.
- 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.
I had same problem, applied patch(CUs) same as at source database server (make both DB server identical) , issue will get resolve.
ReplyDeleteI had the same issue with a customer site, after updating SQL with SP1 CUs and SP2. However, it occurred with the SP1 update and did not improve with the SP2 update. Another result suggested deleting the row referencing version 163 from ServerUpgradeHistory in ReportServer, which did not resolve the problem. Restoring the row/database and deleting the row referencing 164, on the other hand, does seem to work.
ReplyDeleteI had a similar issue with SQL 2014 SP2 using SharePoint 2013 Integrated Mode. Error Found version 162 and Expect Version 163. I ended up deleting the service application preserving the SSRS databases and then recreating the service application in SharePoint 2013. During the process of creating the service application it upgrades the databases for you. After that you need to make sure your service account has access to the databases. Good to go!
ReplyDeleteCommercial applications usually require many fields to be stored like: customer name, company name, address, phone number, and email address. https://www.dbdesigner.net
ReplyDeleteThe 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'.
ReplyDelete