January 15, 2018 at 12:43 am
Dear Everyone
I hope you guys are doing great
I am patching one of our testing SQL Server Databases and the engine gets patched but the Reporting Server table DBUpgradeHistory isnt getting updated on the ReportServer and ReportServerTempDB databases
The SQL Server version is 2014 SP2 standard edition 32-bit and its running on windows 2012 64-bit
The message when i try to run ReportServer on the web is below:
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 '110'. The expected version is '164'. (rsInvalidReportServerDatabase)
On the table DBUpgradeHistory in the ReportServer the versions are below:
UpgradeID DbVersion User DateTime
4 110 SDOBDPB\mngr 2018-01-05 14:36:04.850
3 103 SDOBDPB\mngr 2018-01-05 14:36:04.813
2 102 SDOBDPB\mngr 2018-01-05 14:36:04.790
1 101 SDOBDPB\mngr 2018-01-05 14:36:04.720
But on the same table under ReportServerTempDB i get version 162 so even the temp database for RS is a different version than the RS database
What is happening overhear as i have removed SP2 and reinstalled it and installed CU7 and again no update?
thanks in advance
Kal
January 15, 2018 at 4:35 am
Just an update i have been able to go forward due to insufficient privs but now i am stuck on the issue below:
This may be due to a connection failure, timeout or low disk condition within the database. ---> System.Data.SqlClient.SqlException: Column names in each table must be unique. Column name 'SubType' in table 'dbo.Catalog' is specified more than once.
library!DefaultDomain!2e00!01/15/2018-12:59:24:: e ERROR: Throwing Microsoft.ReportingServices.Library.InvalidReportServerDatabaseException: , 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 '111'. The expected version is '164'.;
So the update did update to version 111 but now its stuck somewhere with the SubType column
Any ideas?
Kal
January 16, 2018 at 2:05 am
Hi Everyone
An update i got the ReportServer upgraded but the TempDB RS didnt and was saying
PK_SnapShotData isnt a constraint
So i deleted this contrainst from ReportServer and it still didnt work
Finally i used the following script to update the values in the table DBUpgradeHistoryto 164 and the RS link worked
Is this acceptable or should we leave SQL Server perform the upgrade its self when starting the RS Configuration Manager?
kal
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply