I am trying to deploy a package using a Microsoft SQL Server Integration Services Designer Version 14.0.800.90, but when I try to execute the package through integration Services Catalogs I get the following error:
The SQL Server version of the destination server is this: 13.0.5149.0 - SQL Server 2016 SP2 CU1 and the ssis product version in the server is 13.0.1601.5
I believe the issue lies on the script component of the data flow inside the package, which in my VS version is higher that in the destination server.
How can I solve this?
In Visual Studio, change the Target SQL Server Version of your project to 2016, then re-build it and deploy it.
I have deployed the entire solution and it worked.
Related
I tried to develop a simple Task but encountred this error
You can try this :
Download and install “SQL Server Data Tools in Visual Studio” the
last version
Repair SQL Server along with client components. This can be done by
choosing option in SQL Setup
I got VS 2017 15.8.1 version installed and a legacy SSIS package created and run in VS 2012 version 11.0.61219.00 Update 5. So basically two VS instances on one machine. I also installed SSDT 15.4.0 version for VS 2017. My app saves .csv file on the server, makes a call to SQL Server 2016 which invokes SSIS packages and passes the address of .csv file to it. SSIS processes the file and saves data to the database. All this is working correctly, however, instead of displaying the uploaded file on page as a link the UI throws the following error.
"Error: 2019-05-09 12:06:03.61, Code: 0xC000F427, Source:
SCR_Chk_UploadTypes, Description: To run a SSIS package outside of SQL
Server Data Tools you must install SCR_Chk_UploadTypes of Integration
Services or higher.,End Error,DTExec: The package execution returned
DTSER_FAILURE (1)."
Any ideas what "SCR_Chk_UploadTypes" is? I'm guessing it might have some relation to SSDT and VS compatibility.
Thanks!
Any ideas what "SCR_Chk_UploadTypes" is? I'm guessing it might have
some relation to SSDT and VS compatibility.
I imagine that is either the name of a connection manager or a Data Source in the data flow(s). Can you post a screenshot?
With respect to the error itself, please note that Microsoft requires a package to target a specific version of SQL Server.
The package that runs in VS2012 can only target SQL Server 2012.
Starting with VS2015, Microsoft introduced the concept of Server targeting. By default, when creating a package in VS2017 the targeted SQL Server will be SQL Server 2017. Have you confirmed that the SQL Server version that the package is targeting is SQL Server 2016?
For more information on targeting
As per the Microsoft documentation on DTEXEC for executing SSIS packages:
When you use the version of the dtexec utility that comes with SQL
Server 2012 Integration Services (SSIS) to run a SQL Server 2005
Integration Services (SSIS) or a SQL Server 2008 Integration Services
(SSIS) package, Integration Services temporarily upgrades the package
to SQL Server 2012 Integration Services (SSIS).
Is there a feature to disable this aspect of DTEXEC utility when running SSIS packages?
My reason for this question is that I have a script task to rename some files in an SSIS package. This works just fine on my local machine and a coworkers local machine, but after deploying this SSIS package to our windows 2012 server with SQL Server 2012 installed I get an error message. I'm really confused, because I wrote this package in SQL Server 2012 Data Tools so this task shouldn't need to be upgraded/migrated at all, which is what the error is complaining about...
Warning: 2016-04-06 11:29:58.14
Code: 0x00000000
Source: DataMergeScriptTask
Description: Found SQL Server Integration Services 2012 Script Task "my_Script_task" that requires migration!
End Warning
Error: 2016-04-06 11:30:03.02
Code: 0x00000001
Source: DataMergeScriptTask
Description: Exception has been thrown by the target of an invocation.
End Error
Unfortunately we haven't found a solution for the Script Task not converting into 2012, as these packages are all written in Data Tools 2012 and opening/resaving the task doesn't seem to actually upgrade the script task in a way that solves it on the server.
My solution has been to take the C# script and turn it into a standalone .exe which has some command line arguments to pass our different parameters with defaults in place to match our current environment. Then I set this up to be executed by a Batch script called by a windows task scheduler job.
I'm hoping to find a real fix for this so that script tasks in larger packages will still be peachy, but that may take more time or a reinstall of data tools... Having multiple versions of SQL Server data tools/BIDS on my workstation could be a cause of this grief. More testing to come!
Just update the TargetServerVersion in your package to match the server version that you plan to deploy to.
Make sure you have a copy of your project in case it doesn't go smoothly. Then right click on the project name, choose properties, then drill into Configuration Properties -> General and update the TargetServerVersion.
Then rebuild and deploy. When the project builds, it should now be in the format that your server expects so it won't try to rebuild the script code on the server where references might not be the same.
The error:
There was an exception while
loading Script Task from XML: System.Exception: The Script Task
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)
I'm doing exactly what it says, but it does not help.
Any solution?
This worked for me:
Install SSDT-BI for Visual Studio 2013.
Open your solution in Visual Studio 2015.
Select your SSIS Project in the Solution Explorer.
In the Project menu select Properties.
In the Property Pages dialog select Configuration Properties -> General
Under Deployment Target Version change the Target Server Version to "SQL Server 2014."
Clean and rebuild solution and redeploy.
In the revised version of the SSDT (now 14.0.61x), there is a fix.
Install new version. (SSDT For download)
Right click project > Properties > Configuration Properties > General > TargetServerVersion - Update to SQL Server 2014 > Redeploy.
Even though this question is a bit dated, I am getting the same error on the targeted server, but in a slightly different context:
created an SSIS package targeting SQL Server 2014
add a script task
deployed it to SQL Server 2014
package validation failed with "The Script Task uses version 15.0 script that is not supported in this release of Integration Services..."
I used the following environments for the development and deployment:
VS2015 Update 3
SSDT v 17.1
Deployed using SSMS v17.1
The current SSDT version 17.1 provides a support to target SQL Server 2014 - SQL Server vNext. The current version of the SSDT resolves the issue in the question by providing targeted option in the project configuration as already mentioned.
I noticed that the above SSIS project works on the targeted server if deployed with:
VS 2015 (Select SSIS Project -> Right Click -> Select Deploy)
SQL Server 2014 SSIS Deployment Wizard (probably available only if you have a local instance installed; found in the Microsoft SQL Server 2014 Windows Start Menu)
If you try to deploy it using SQL Server Management Studio v17.1 version of the SSIS Deployment Wizard the deployed package fails. The deployed script task is deployed as version 15.0 that is not supported on the SQL Server 2014.
If I deploy the same package using SSIS Deployment Wizard from Microsoft SQL Server vNext CTP2.0 Windows Start Menu, which probably got added by installing SSMS 17.1, the deployed package script task fails with same error.
In summary:
The latest SSDT v17.1 for VS2015 resolves above issue by providing targeted server configuration options
It needs to be deployed through Visual Studio 2015
It can be deployed using the targeted server version of the SSIS Deployment Wizard
If using the latest SSMS v17.1 and build-in SSIS Deployment Wizard the SSIS package Script Task will fail on the targeted server for being upgraded to SQL Server 2017 version
Maybe this is by design, but it is very confusing and caught me of guard. Just in case this is a bug I submitted a bug report.
I think I can probably guess that the answer to this question is going to be NO!
Here goes anyway... I have developed an SSIS package on my local development machine with SQL Server 2008R2 installed.
When I went to deploy on the production server the package failed with all sorts of errors. After digging around I discovered the production server is running SQL 2008 (not R2).
Question: is there a simple way (preferably some simple setting in the IDE) that will make my package compatible?
UPDATE: This is the exact error I get when I try to execute the package on SQL Server(R1)
Description: Microsoft.SqlServer.Dts.Pipeline.ComponentVersionMismatchException:
The version of component "ADO NET Destination" (79) is not compatible with
this version of the DataFlow. [[The version or pipeline version or both for the
specified component is higher than the current version. This package was probab
ly created on a new version of DTS or the component than is installed on the cur
rent PC.]]
It seems ADO NET destinations are the only incompatible things between 2008 and 2008R2. For a solution, see:
http://agilebi.com/jwelch/2010/05/13/moving-ssis-packages-with-ado-net-destinations-between-2008-r2-and-2008/