SSIS and Visual Studio 2019 – Issues and fixes

I recently wanted to try out Visual Studio 2019 with the SSIS Package designer (and to also try out the KingswaySoft extensions for dealing with Dynamics 365 data integration/migrations. Getting it all to work turned out to be a little bit of a challenge, so here I am documenting the issues I encountered, and what I did to fix it.

Installing SSIS for Visual Studio 2019

With VS 2019, the method of installing the tools has changed. Its not a tool you install separately, its an extension, although I would argue that installing the extension does in fact just download a separate installer.

You first need to ensure that you have installed the main “Data storage and processing” tools as part of the Visual Studio installation routine. So, either choose the following option when installing Visual Studio, or if its already installed, run the Visual Studio Installer application, and make sure you add in this option.

Once that is installed, you need to go to the extensions window in Visual Studio and find the following extension, download and install it.

Once that has been installed, the SSIS project templates will be available, and you can access the SSIS Toolbox from those project types, or can you???

Broken SSIS Toolbox

Not on all machines, but certainly on my Surface Book, the SSIS Toolbox can fail to work. The Getting Started (SSIS) window can also fail. It ends up blank, and in fact, the window looks to be unresponsive, and will often show the previous window graphics within it, like the below screenshots.

Turns out the issue is to do with DPI scaling and the rendering engine. This probably only affects High DPI screens (such as the Surface Book), but it was quite an easy fix once I found it on the old “google”.

Just go in to the Visual Studio options, and turn off the following option and restart Visual Studio.

Once done, problem solved, and the SSIS Toolbox should now show as normal.

Installing KingswaySoft Integration Toolkit for Dynamics

I did not expect this element to be troublesome, but it was. The latest version (at the time of writing was version 11) would install, but, no matter what I tried, I could not get the toolbox items to show up.

It turns out, to be able to get them to work (at least in my case), I had to download the manual install pack (which currently is only available for version 10) from the following website.

By downloading the manual install, and extracting the file, I was able to open up a command prompt as an administrator, and run the “install_sql2017.bat” file, and it installed the appropriate tools which then showed up in Visual Studio.

As a small footnote, I did actually (in my case) have to modify the batch file first as the line that actually used the gacutil.exe to register the assemblies would not work. It was coded to point to a specific location for the utility as part of the .NET framework installed, and my machine had a different version, so I modified the path to point to the correct one.

As an example, one of the lines read:

“%programfiles(x86)%\Microsoft SDKs\Windows\v10.0A\bin\NETFX 4.6.1 Tools\gacutil.exe”

and I had to change it to:

“%programfiles(x86)%\Microsoft SDKs\Windows\v10.0A\bin\NETFX 4.7.2 Tools\gacutil.exe”

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s