Unable to deploy SSIS packages from Visual Studio 2017 (15.8.0)
The latest version of Visual Studio 2017 (15.8.0) appears to have introduced a bug preventing deployment of SSIS project files.
When attempting to connect to a server the deployment wizard returns the following error:
TITLE: SQL Server Integration Services
Could not load file or assembly 'Microsoft.SqlServer.Management.IntegrationServicesEnum, Culture=neutral, PublicKeyToken=89845dcd8080cc91' or one of its dependencies. The parameter is incorrect. (Exception from HRESULT: 0x80070057 (E_INVALIDARG)) (mscorlib)
The parameter is incorrect. (Exception from HRESULT: 0x80070057 (E_INVALIDARG)) (mscorlib)
Please fix it ASAP
Matt Benham commented
Same issue here. Also affects package model deployment for 2016+. Trying to downgrade now which is proving difficult due to a "maximum recursion error".
Pages where this error is also described:
Syed Shahid Hussain commented
Terrible update, please fix it ASAP.
same problem here. Pls fix
I have the same issue starting this week. I have been tearing my hair out for the past two days as this was a normal operations step I didn't need to troubleshoot. Running the UI deployment wizard on the .ispac file straight from SSMS was my workaround.
I didn't even mean to update VS. I was just trying to learn some new VS techniques and accepted an update so I could try a different feature.
LL SQL DBA commented
We are SSMS 2017. (v17.8.1)
If we try to deploy and ISPAC using SSMS 2017 to an SSIS DB server running SQL 2016, it fails with a similar error.
Our work around is to log in locally to the server and use SSMS 2016 that we installed locally on the server.
Same issue here.
Carlos Muñoz Rodriguez commented
Same issue here. Doesn't work with 15.8.1 either
Mark Gelderblom commented
Unbelievable that Microsoft still does not test the SSDT after a new Version of VS !!!!
This has happened too many times now, really bad show
Same here, painfull to be punished for neatly staying up to date with VS2017.
Having the same issue. Workaround posted by John Mihalko works fine for now.
Dear Microsoft, please fix this ASAP. Don't your dev / QA teams don't talk to each other. ???
John Mihalko commented
The work around that worked for me is to build the project and then navigate to the bin folder and double click the .ispac to open the SSIS deployment wizard outside of Visual Studio (if ispac file extensions are mapped to the Deployment Wizard). Or open the Deployment Wizard from the Windows menu.
I am having the same problem when I try to connect to an SSIS/SQL server to import the SSIS packages to VS2017. This problem only began once I updated VS to 15.8.0.
Jez Walters commented
This is a VERY inconvenient impediment!
Piotr Śmigielski commented
Hi, I'm having the same issue. Seriously people we cannot work normally !