Microsoft Visual C# Versioning Error

Question

Locally we are developing a SSIS Package in Microsoft Visual Studio 2017 and specifically a C# Edit Task defaulting to and using ScriptLanguage Microsoft Visual C# 2017. Runs perfect locally.

But when we moved the .dtsx to our Production Job Server and attempted running through our Production Job Server and a SQL Server Agent Job, it blew up with the following message.

Description: There was an exception while loading Script Task from XML: System.Exception: The Script Task "ST_d2eaec3757c64bbe937ea17da8a504e3" 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)

Now if I try building this on our Production Server, Our Production Server has Microsoft Visual Studio 2013 Version 12.0.21005.1 REL and if I create a project on our Production Server and Visual Studio 2013, the C# Edit Task on the Production Server is using ScriptLanguage Microsoft Visual C# 2012

Obviously looks like a versioning error for Microsoft Visual C# between my locally developed .dtsx SSIS Package and what the Production Job Server has installed on it.

So my question is two-fold.

Do I have to get our network engineers to upgrade something on our Production Job Server so that this .dtsx SSIS Package can run successfully? If so, is that a Microsoft Visual Studio upgrade? Microsoft Visual C# upgrade? Will that effect anything else? Like existing SQL Server Jobs that use SSIS .dtsx and C# Edit Scripts?

Or is there any way I can change the Microsoft Visual C# ScriptLanguage locally on my Visual Studio Project to make it compatible to what's on the Production Job Server?

We don't wanna mess this up...so can anyone please direct me as to the best way to go about fixing this?

Thanks for your review and am hopeful for a reply.

Answer 1

Hi

versioning

Best Regards.

Please click the Mark as answer button and vote as helpful if this reply solves your problem.

Answer 2

Steps to fix the issue:

1. In VS2017 on a dev. machine you need to set TargerServerVersion value that matches your SSIS run-time version on the server.
2. Open Script Task and build it via the menu Build. It will recompile the Script Task code to match the server.

Please see below:

Answer 3

Hi @Bobby P ,

Please set the Target Server Version as the same as the version of SQL Server in your Production Job Server .

Please refer to the following link:
Backwards Compatibility in SQL Server Data Tools for Integration Services

Best Regards,
Mona

----------

If the answer is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.