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)
Nikolay Kojuharov commented
The issues are NOT fixed in 14.0.16179. There are still issues - e.g. create folder doesn't work - it errors with exception about Microsoft.SqlServer.BatchParser, Version=184.108.40.206 not being found.
Matt Benham commented
Has this issue come back again? My trial VS license (that I installed to avoid this problem) just expired so I installed SSDT from scratch again. I now have the problem again. It is showing as version 15.9.1, build 15.1.61810.11040 . What is going on with Microsoft quality control!
People... please read the comments below.
This was already fixed in update 14.0.16174.0 of SSDT!
Changelog here: https://docs.microsoft.com/en-us/sql/ssdt/changelog-for-sql-server-data-tools-ssdt?view=sql-server-2017
1. Update your Visual Studio SSDT Component with the Visual Studio installer.
2. Download and install the *standalone* Version of SSDT here: https://docs.microsoft.com/en-us/sql/ssdt/download-sql-server-data-tools-ssdt?view=sql-server-2017
Can someone mark this Issue as fixed please?
Tony Lyle commented
Same issue here, just getting my name on the list..
Tuomas Rantanen commented
I have found out that if you encounter this problem (or some other random error) after update (installed update from Visual Studio, Tools->Extensions and Updates) problem can be fixed by uninstalling SSDT and Visual Studio and installing them again. Everything should be working again after that. The version update installation process is the probable source of the problem.
Henry Grimes commented
Finally fixed for me now. Updated VS to 15.8.7. Uninstalled SQL Data Tools IS, AS, RS Projects from VS and then installed the latest SQL Server Data Tools (https://docs.microsoft.com/en-us/sql/ssdt/download-sql-server-data-tools-ssdt?view=sql-server-2017) which shows as Version 14.0.16179.0 in Add/Remove Programs.
Kristian Svedal commented
Had no issue with package deployment in SSIS from within SSDT before recently upgrading to 15.8.6. Receiving same error message as OP.
Phil D commented
15.8.6 same error on prem
15.8.6 same kind of issue, thanks
15.8.6 same kind of issue
Sergej Steinhauer commented
It works for me after Update VS 2017 to 15.8.3 and reinstall SSDT from posted link.
Allegedly fixed in the current Release of SSDT version: 14.0.16174.0 - Release date: September 05, 2018.
I can not test it right now. Can anyone confirm?
Tom Adams commented
Just check after updating to 15.8.3 still broken
This is fixed in the newest release, buil number 14.0.16174.0:
Why did we ever upgrade from VS 2008...
Same Issue, its Annoying.. rolling back to older version is a poor solution. I cant deploy to catalog. Please fix it soon.
Matt Benham commented
Agreed Boka, similarly in addition to the deployment issues, I had a working project suddenly crash VS without error every time upon build. It builds fine after installing an older (trial) version of VS. Didn't bother investigating further as I couldn't deploy anyway. The deploy issue may have just scratched the surface of problems in these versions.
You can deploy ispac as a workaround but during execution I'm getting unreasonable validation errors. After deploying the same project from different PC with older SSDT error disappear. Deployment is completely messed up. Turn it back prior to 15.8
Same issue. It's hard to convince ppl to use the catalog when you Visual Studio can't even deploy to it.
Just installed 15.8.2 and problem still exists. You can use other deployment tools but it's really annoying!