Forum Discussion
Solved
VS2019 with SSIS extension 4.5 crashes when setting target version to SQL Server 2016
After completely re-installing VS2019 and SSIS extension 4.5 I'm not able to develop an SSIS package in which I set the TargetServerVersion to SQL Server 2016. If I create a new SSIS package then...
Today I discovered that I also have a local VM on which VS2019 + SQL Server 2019 + SSIS extension 4.5 was installed. On this VM I could switch to target version 2016 without problems. So I started comparing the folder contents between the VM and my local PC.
It appeared that on my local PC the folder "C:\Program Files (x86)\Microsoft SQL Server\130" only contained two folders LocalDB and Shared whilst on my VM this folder also contained a DTS, SDK, 'Third Party Notices' and Tools folder. I decided to copy the complete contents of "C:\Program Files (x86)\Microsoft SQL Server\130" from my VM to my local PC. After this action my problem is solved.
Looking at the timestamps of the "C:\Program Files (x86)\Microsoft SQL Server\130\DTS" folder on my VM then I conclude that this folder should be installed as part of the SSIS 4.5 extension installation. However I re-installed the SSIS 4.4, 4.5, 3.16 several times on my PC and this never resulted in the installation of the "C:\Program Files (x86)\Microsoft SQL Server\130\DTS" folder. I can only assume that the SSIS 4.5 installation package looks at some registry keys and based on that decides to skip the installation of "C:\Program Files (x86)\Microsoft SQL Server\130\DTS" folder. Otherwise I have no other explanation for the behavior that I observed.
Today I discovered that I also have a local VM on which VS2019 + SQL Server 2019 + SSIS extension 4.5 was installed. On this VM I could switch to target version 2016 without problems. So I started comparing the folder contents between the VM and my local PC.
It appeared that on my local PC the folder "C:\Program Files (x86)\Microsoft SQL Server\130" only contained two folders LocalDB and Shared whilst on my VM this folder also contained a DTS, SDK, 'Third Party Notices' and Tools folder. I decided to copy the complete contents of "C:\Program Files (x86)\Microsoft SQL Server\130" from my VM to my local PC. After this action my problem is solved.
Looking at the timestamps of the "C:\Program Files (x86)\Microsoft SQL Server\130\DTS" folder on my VM then I conclude that this folder should be installed as part of the SSIS 4.5 extension installation. However I re-installed the SSIS 4.4, 4.5, 3.16 several times on my PC and this never resulted in the installation of the "C:\Program Files (x86)\Microsoft SQL Server\130\DTS" folder. I can only assume that the SSIS 4.5 installation package looks at some registry keys and based on that decides to skip the installation of "C:\Program Files (x86)\Microsoft SQL Server\130\DTS" folder. Otherwise I have no other explanation for the behavior that I observed.