Recently one of my old clients contacted me for an error execution via SQL Agent Job. They informed that it runs fine when they invoke the package from Visual Studio (SSDT). In this blog post, we will discuss Exception While Loading Script Task from XML.
Here is the error which was seen in SSISDB reports via management studio.
Script Task 1:Error: There was an exception while loading Script Task from XML: System.Exception: The Script Task “ST_24802bd6f41940e0befad660c2cba337” uses version 15.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)
The error message is good enough in telling the cause. The script task version is 15.0 and SQL SSIS version is not compatible. Our target version was SQL Server 2016.
WORKAROUND/SOLUTION
When I checked various version, I found that the SSIS package was developed with Azure features packs on SSDT 2017. Since we are deploying it in SQL server 2016 and running via agent job, it is throwing an error.
To fix the problem, all we needed to do was change the TargetServerVersion values under project properties as shown below.
Have you encountered a similar error? Please comment and let me know if you found some other solution?
Reference: Pinal Dave (https://blog.sqlauthority.com)
First appeared on SQL Server Integration Services (SSIS) – There Was an Exception While Loading Script Task from XML