This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(316.8, 82%, 40%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ETD%3C/text%3E%3C/svg%3E)
Testing a new sql server database server (widows 2019/ sql server 2019).
The old server is windows 2012r2 / sql server 2014
We are running sql agent jobs that call SSIS packages from the SSIS Integrations Services Catalogs.
Initially we deployed projects from old server to the new server (from the SSISDB database, Visual Studios was not involved).
Then we ran sql agents jobs and they worked.
Then to make sure deployment from visual studios still works, from visual studios, I deployed the source code to the new sever by right clicking on the project in visual studios and choosing deploy. There are no errors in the deployment. Before deploying I did a build and there were no errors.
We ran many packages.
After that visual studios deployment to the new server the packages that run a c# script failed, every package that did not run a c# script succeeded on the new server.
The ScriptLanguage is Microsoft Visual C# 2012
I read a post that said to rebuild the scripts in visual studios before deploying. I tried that and it did not help.
I then used visual studios and deployed the packages to the old server.
Then we ran sql agents jobs on the old server and they worked.
Everyone succeeded, same source code.
On the new server the run errors when running the sql agent jobs (or from right clicking and execute from SSISDB) are:
For the package called -REPO_APPL - script for 2 location ind concat failed validation
-The binary code for the script is not found.
For the package called -ER_ERRORLOG
For the package called ER_PERSONNEL_COST rerun on error reset LoopCntr to exit
Here is our version of Visual Studios:
Microsoft Visual Studio Ultimate 2013
Version 12.0.40629.00 Update 5
Microsoft .NET Framework
Version 4.6.01055
Summary:
Success running packages on the server with deployment from old server to new server. Failure running packages after deploying from Visual Studios to new sever.
I can deploy from visual studios to the old server, and then deployed that from the old server to the new server and packages will run fine.
That's kind of a crazy work around to get code enhancements to the new server as we want to get rid of the old server.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(140.8, 78%, 23%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ETS%3C/text%3E%3C/svg%3E)
Hello @Tietz, Derrick , thank you for taking time to post this issue in Microsoft Q&A forum. Have you tried to set the TargetServerVersion and select the SQL Server 2019 for Deployment Target Version(From property page of your project) before deploying to new server?
I'm using Microsoft Visual Studio Ultimate 2013 and from what I see, that version does not have TargetServerVersion as an option.
I saw this post - Note: Starting from Visual Studio 2015, Microsoft introduced authoring SSIS Packages for multiple versions (i.e. Same Visual Studio version can be used to edit packages for 2012, 2014, 2016, vNext). Also, you can Upgrade or Downgrade SSIS package format in few clicks (see below steps)
We just did an experiment. The dba ran the package from ssis integrations catalogs and it worked but when I try it it fails. I have sysadmin on the data base. The dba is looking into security - maybe it's file system security somewhere?
Hi @Tietz, Derrick , thank you for your feedback. Yes, the option TargetServerVersion will be shown after you install Visual Studio 2015(or VS 2017, VS 2019), otherwise it will not be shown in Visual Studio 2013(right-click your project > Properties > Configuration Properties > change the TargetServerVersion). If possible, I may suggest you try to install VS 2015 and change the TargetServerVersion. Here is a similar thread: The binary code for the script is not found for you to refer to.
I'm trying now to upgrade the project to 2017.
I tried to open the package in 2017 (it was in 2013). I got this error:
Unsupported
This version of Visual Studio is unable to open the following projects. The project types may not be installed or this version of Visual Studio may not support them.
For more information on enabling these project types or otherwise migrating your assets, please see the details in the "Migration Report" displayed after clicking OK.
Non-functional changes required
Visual Studio will automatically make non-functional changes to the following projects in order to enable them to open in Visual Studio 2015, Visual Studio 2013, Visual Studio 2012, and Visual Studio 2010 SP1. Project behavior will not be impacted.
I checked to see what was installed on the server and it lists 'Microsoft Integration Services Projects' as installed.
I can now go ahead and try to upgrade to 2017 because visual studios 2017 has been reinstalled and recognizes my project now.
(re: SSDT installer for Visual Studio 2017something probably got messed up and a re-install/update fixed it)
I upgraded from ssis 2013 to 2017 as suggested by TianyuSun-MSFT avatar imageTianyuSun-MSFT.
I set the project > Properties > Configuration Properties > TargetServerVersion to 2017.
Then I did a build and deployed to the server. Now it works.
I no longer get this error - "The binary code for the script is not found.