I stumbled across an error message that didn’t seem like was getting much exposure online so I wanted to write it up here just case anyone else had this experience. The situation that created this issue was a Visual Studio 2015 development environment creating packages that would get deployed to a SQL Server 2014 instance. When running the package through a SQL Agent Job I would get the following error in the reporting log.
“SCR Build ErrorMessage text 1:Error: There was an exception while loading Script Task from XML: System.Exception: The Script Task “”ST_c9f9ef4bd6a84f25a6cca6ce603450c5″” uses version 14.0 script that is not supported in this release of Integration Services. To run the package, use the Script Task to create a new VSTA script. In most cases, scripts are converted automatically to use a supported version, when you open a SQL Server Integration Services package in %SQL_PRODUCT_SHORT_NAME% Integration Services.
at Microsoft.SqlServer.Dts.Tasks.ScriptTask.ScriptTask.LoadFromXML(XmlElement elemProj, IDTSInfoEvents events)”
Initial online research suggested that the scripts that were in use for these packages were corrupt and or outdated and that they needed to be reapplied if these objects originated from earlier Visual Studio versions. That was not the case in my scenario as I just need some updates and a quick configuration.
When the early versions of SSDT for 2015 were released they were only supporting SQL Server 2016 deployments. Later releases would add the functionality to deploy to a SQL Server 2014 instance. These later releases of SSDT are extremely helpful as the recourse would be to develop your packages under Visual Studio 2013.
After doing some searching online it was found that as of this writing the Microsoft recommendation is to apply the latest Visual Studio Updates. Instruction can be found here.
Applying the latest Visual Studio Updates does not automatically correct the 2014/2016 compatibility issue. There is some configuration to apply. Right click on your project and select Properties. Under Configuration Properties select General. Set your desired TargetServerVersion and that will allow you to apply that property to all of your packages. Now redeploy and you should have successful package executions on SQL Server 2014 instances.