SSISDB Upgrade Failure
SSMS 17.8 contains a bug with SSISDB, specifically, when connected to a SQL Server 2016 SP2 CU1 instance (locally on the same server), if you restore a SQL backup of SSISDB from a 2014 instance and select "Database Upgrade" from Integration Services Catalogs - you get the following exception:
Object reference not set to an intance of an object. (Microsoft.SqlServer.IntegrationServices.UITasks)
Inner exception of which is:
Microsoft.SqlServer.IntegrationServices.UITasks.Helpers.GetDtsSetupPath(string subKeyName).
This issue occured with SSMS running normally, and when elavated as Administrator.
During a recent upgrade we were forced to abandon our 2014 SSISDB upgrade and create a new blank catalog on the 2016 instance and manually republish all our packages.
Screenshot attached showing error in question
HeavenCore
shared this idea
5 comments
-
Emil Vissing
commented
ISDBUpgradeWizard is broken after SQL Server 2019 CU2 it looks like..
-
Rubén Garrigós
commented
Same happening with SQL Server 2019 CU2. It was expected to have it solved but it is not...
-
Rubén Garrigós
commented
Same happening with SQL Server 2019 CU1. There is a version mismatch, after installing the CU the ISDBUpgradeWizard.exe is still RTM and the SSISDB upgrade fails miserably.
-
David Heath
commented
This seems to be an issue if the SQL instance has been upgraded/patched after the initial install. The service pack or CU update changes the SQL instance version, but the ISDBUpgradeWizard.exe application doesn't get upgraded. If you run the application manually, you get a failure saying the instance is a different version to the upgrade application. A way around this is to install a new instance of SQL server 2016, restore the SSIDB from 2014, do the database upgrade, then restore the database to the final 2016 instance. It will then have the new table structure in it.
-
Yide Tu
commented
You can run the SSISDB upgrade wizard directly from C:\Program Files\Microsoft SQL Server\140\DTS\Binn\ISDBUpgradeWizard.exe
