I\'ve recently taken over a SSIS ETL based process and due to some licencing issues I had to upgraded from Data Tools 2013 to 2015. Most of the project survived the upgrade and
If you change Target Server Version for the project, as described in the other answers, make sure to check that you've done so for the applicable configuration(s) that you are deploying (Development, Test, Production).
In my case changing SSIS packages to 32/64 bits, and setting target SQL version have not worked.
If you have this issue even if you set SQL Target Version to 2016, make sure that you are using correct version of SQL Server Deployment Wizard. If you are trying to deploy package on SQL2016, make sure that you have ISDeploymentWizard:
C:\Program Files (x86)\Microsoft SQL Server\130\DTS\Binn Server\130\DTS\Binn\ISDeploymentWizard.exe
If not, you have to install SSMS dedicated for SQL Server 2016 (download link) which will install ISDeploymentWizard. Backward compatiliby in higher version of SSMS will not install ISDeploymentWizard.
Probably ISDeploymentWizard for higher versions upgrades SSIS package to higher version, and SQL Server cannot downgrade it.
I tried to update the only elelment which I haven't touched - SQL Server 2014, but with no impact. Eventually I decided to take full ownership of process and worked around it by pushing down the logic to the database.
I had faced the same problem "Error Code: 0xC0048021" and solved it.
I installed this version of SSDT from here https://msdn.microsoft.com/en-us/mt429383
Then, in the SSDT solution explorer right click the Project,go to the Properties --> Configuration Properties --> TargetServerVersion = SQL SERVER 2014
Then, in the SSDT solution explorer right click the Project, go to the Properties --> Configuration Properties --> Debugging --> Run64BitRuntime = False
Referring to this link http://blogs.msdn.com/b/ssis/archive/2016/03/03/what-s-new-for-ssis-2016-rc0.aspx