SOLVED

VS2019 with SSIS extension 4.5 crashes when setting target version to SQL Server 2016

Copper Contributor

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 as long as the SQL target version is 2017 or higher then everything is working perfectly.  However if I create a new empty SSIS package then as soon as I change the SQL target version to 2016 VS2019 crashes with the exception as shown below.

 

What I observe is that as soon as I change the target version to SQL Server 2016 then SSIS does not show a toolbox anymore. If for example one Execute SQL Task was already added to the package then I get a strange square icon with arrows and the error 0x80070057 "The parameter is incorrect" followed by a crash of VS2019 (see screenshot below).

 

My first question is, does SSIS extension 4.5 officially still support 2016 as target version because I read different answers on the internet. Secondly what I'm missing to switch to SQL Server 2016?

 

Any help is welcome because I already spent more than one day on solving this issue without success.

 

FYI: I already tried several times to completely re-install VS2019 and the SSIS extensions. I even tried SSIS extension 4.4 and 3.16 but all result in the same VS2019 crash.

 

Erik_Bijsterveld_0-1710321774781.png

 

VS2019 exception in Application eventlog:

Faulting application name: devenv.exe, version: 16.11.34601.136, time stamp: 0x65bc1189
Faulting module name: KERNELBASE.dll, version: 10.0.19041.4046, time stamp: 0xa0505aa2
Exception code: 0xe0434352
Fault offset: 0x0013fa72
Faulting process id: 0x2efc
Faulting application start time: 0x01da751cc5bda5f9
Faulting application path: C:\Program Files (x86)\Microsoft Visual Studio\2019\Professional\Common7\IDE\devenv.exe
Faulting module path: C:\WINDOWS\System32\KERNELBASE.dll
Report Id: 9c019a44-1e19-4780-9464-184fa73ff0e4
Faulting package full name:
Faulting package-relative application ID:

1 Reply
best response confirmed by Erik_Bijsterveld (Copper Contributor)
Solution

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.

1 best response

Accepted Solutions
best response confirmed by Erik_Bijsterveld (Copper Contributor)
Solution

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.

View solution in original post