Deploying SSIS Package - 'Failed to load Assembly Microsoft.SqlServer.Management.IntegrationServicesEnum'

Question

I have a fresh install of SQL Server 2016 Developer with SSIS, on a clean install of Windows 10

When I try to deploy an SSIS package (developed on the same machine), when I come to select the destination server, I instantly get an error;

Failed to load assembly Microsoft.SqlServer.Management.IntegrationServicesEnum

Selecting 'details' doesn't seem to add much

Could not load file or assembly Microsoft.SqlServer.Management.IntegrationServicesEnum, Cluture=Neutral, PublicKeyToken=xxx

I've tried doing a repair on the install, to no avail. I've also tried referring to it as both the proper computer name, and localhost, but gives the same error

It's not my first time setting up SQLS & SSIS, but don't recall having any such issues before. The catalog has been created, but wonder if I've missed something out.

Solution 1

Ok, here are the steps I took to resolve the issue (eventually!)

• I uninstalled all programs relating to Sql Server Data Tools (inc Management Studio, SharedManagementObjects) and anything related to Visual Studio, leaving pretty much just the core database engine and SSIS.
• I performed a 'repair' on what was left of my SQLS installation, mainly to restore anything I'd removed that I shouldn't have
• I then re-downloaded & installed Sql Server Data Tools & Management Studio

Everything now seems to be working as it should.

Solution 2

This bug in some versions of VS data tools can be avoided by running the deployment wizard directly instead of opening it via visual studio.

Locate ISDeploymentWizard.exe for correct version of SQL server, e.g.

C:\Program Files\Microsoft SQL Server\140\DTS\Binn\ISDeploymentWizard.exe

Double click to run the exe then select your .ispac project file, e.g.

C:\SSISProject\bin\Development\SSISPackage.ispac

The deployment wizard should now complete without error.

Solution 3

I performed a repair from the data tools setup menu, and this seems to have solved it

Comments

[Nick.McDermaid]

For this flaky unreliable tool, sometimes it's the only solution

[Nick.McDermaid]

You can also just use this wizard straight from SSMS by right clicking on a project folder

[Hairy Drumroll]

Further to @Nick.McDermaid's comment, there is documentation on how to do this.