Did you try to right click project > Properties and see if you can update SQL 2014 version from there
----------
Please don't forget to Accept Answer and Up-vote if the response helped -- Vaibhav
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
We are testing Integration Services Catalogs with SQL Server 2014. We are trying to find a way to deploy from Visual Studio. When we try from Visual Studio 2017 Pro (with data tools) we receive the following error.
![18800-image.png][1]
I'm trying to determine if these two are even compatible. This Microsoft page says VS 2017 is compatible with SQL Server 2014, but doesn't specifically say if it is compatible with 2014 SSIS and SSISDB.
Did you try to right click project > Properties and see if you can update SQL 2014 version from there
----------
Please don't forget to Accept Answer and Up-vote if the response helped -- Vaibhav
Hi alhowarthWF,
In SQL Server Data Tools (SSDT), you can create, maintain, and run packages that target SQL Server 2017, SQL Server 2016, SQL Server 2014, or SQL Server 2012.
In Solution Explorer, right-click on an Integration Services project and select Properties to open the property pages for the project. On the General tab of Configuration Properties, select the TargetServerVersion property, and then choose SQL Server 2017, SQL Server 2016, SQL Server 2014, or SQL Server 2012.
Please refer to Version targeting in Integration Services projects.
Best Regards,
Mona
----------
If the response is helpful, please click "Accept Answer" and upvote it.
Thanks to both for the suggestions. I had not set the version. Unfortunately, that did not fix it. Although, after I set the version, I did receive a better error.
The parameter is incorrect. (Exception from HRESULT: 0x80070057 (E_INVALIDARG)) (mscorlib)
I researched that error and found there is an bug in some versions of SSDT. https://developercommunity.visualstudio.com/content/problem/311891/error-deploying-ssis-package.html
I was able to use the workaround of launching the .ispac file to deploy.
Thanks again,
Al