SSIS packages fail when targetserverversion is sql server 2019

Question

I have had several packages running for quite a while -since they were created and deployed to Prod a couple of years ago- with targetserverversion set to sql server 2019.

From time to time, some of them have required adjustments. Not a problem to implement those changes and taking updated packages to Prod.

Then, all of a sudden packages failed to run from data tools. The only thing that changed is the recent update applied to VS/Data tools (16.11.16).

Even if you create a new solution with a new project and a new blank package and try to run it, I will get this error:

Because of number 160 after application -see the error message- I thought, why is it referencing a number related to sql server 2022. Then I tried changin targetserverversion to any other version -sql server 2022- included and the package runs.

Is this a bug related to the las VS update?!

Answer 1

Hi @Juan Carlos Solano ,

No need for any Data Tools (SSDT). It was applicable for VS2017 and earlier.

For SSIS packages development in VS2019 you need to use SQL Server Integration Services Projects extension for VS2019.
Please make sure that its version 3.16 is installed on your machine.

And ignore Version 4.0 preview for now.

Here is a download link: SQL Server Integration Services Projects

Answer 2

Thank you @Yitzhak Khabinsky , I can't believe such a rookie event were the cause.
Since SSIS add-ons need to be installed manually I did not notice this latest update was a review version.