I have recently upgraded my SSIS package from 2015 to 2017.In one such package a script task is present in which after deployment if opened in visual studio 2017 an warning pop up FOUND SQL SERVER INTEGRATION SERVICES 2012 SCRIPT TASK <SCRIPT TASK NAME> REQUIRES MIGRATION. What is the exact cause of this warning? Have executed the package and it works properly through SSDT and job.
Related
This error just started occurring on a few developers' systems across several packages, but I can't track down a specific cause or update. We have SSIS processes created across various targets (SQL 2012 and up), but when I open them in Visual Studio 2019 this error occurs:
Error loading XXXXXXX.dtsx: There was an exception while loading Script Task from XML: System.Exception: The Script Task "ST_36ae893a14204fac97ce8ce3b4ce8ebb" uses version 16.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)
I can open the script task, but it's as if it's new, none of the existing code is there. Some of the older packages I can open in like Visual Studio 2017 and they work, but in Visual Studio 2019 not so much. Even some packages built in Visual Studio 2019 are doing this. Here's my dev environment:
Microsoft Visual Studio Enterprise 2019
Version 16.11.17
VisualStudio.16.Release/16.11.17+32630.194
Microsoft .NET Framework
Version 4.8.04084
SQL Server Data Tools 16.0.62205.05200
Microsoft SQL Server Data Tools
SQL Server Integration Services 16.0.948.0
Microsoft SQL Server Integration Services Designer
I've tried changing the Target server to different versions, but it seems once the issue occurs it resets the script task removing all code. I'm really confused.
Any thoughts? Thanks.
Not sure if this is a good answer, but it does seem to fix the issue. I'm using SQL Server Integration Services 16.0.948.0 (v4.3), but if I go back down to 15.0.2000.180 (v3.16) the issue seems to go away. So, it's something with version 4.0 and up. Not ideal to go backwards as we're losing some of the updates - but it gets me going again. If anyone has other suggestions, please let me know.
SQL Server on a SSIS server has been upgraded to SQL 2017 from 2016
SSIS Packages are built in projects that Jenkins runs as a BIML Build (BIML Studio 2018) on a Build Server
Visual Studio Standalone has been upgraded as has the project deployment file
When we change the jenkins job to look for 2017 it thinks its looking for 2012. The environment variable in jenkins reflect what we see in the Windows PATH environment variable
When its run as 2016 the BIML Build runs fine, but the connections, script tasks, merge commands have script errors - see image link.
Error Screenshot
The scripts are built in C# and used to build each component for SSIS.
We need to know what the likely cause of the errors in SSIS are.
We are upgrading from Sqlserver 2012 to 2019 in that process we need to migrate our SSIS packages also from 2012 to 2019. We have lot of script task which uses connection string and other configurations from DtsDebugHost.exe.config It was loaded from Binn folder of Sql server installation folder by default in sql server 2012. but in sqlserver 2019 we couldn't figure out from where it is loaded to the appdata local folder. So our script task is failing because it couldn't acquire connection and couldn't resolve the libraries ( which are used in our config).
I have SSIS package with a script task to access excel files. When I deploy the package to SQL Server 2014 and run manually from SSIS Catalog its working fine.
But when I run the same package after creating a job, it fails with below error
Please suggest an FIX
I know this do the trick by deploying pkg through Visual Studio as I was also facing the same issue.
But recently my DBA, told me that he is not fine with installing visual studio on PROD in order to deploy packages. Is there any workaround for this as I can't install visual studio on PROD server still want to get rid of this error.
I tried degrading pgk version to 2015/2016 in TargetServerVersion but it didn't work, still facing the same issue.
Do we have to have visual studio if our SSIS pkg contain script task ?
I faced that issue before and the fix was registering the dll in the server. You don't need to install VS.