SSIS error - version number in package is not valid

Question

The logs for the failed job are as follows:

11/04/2014 06: 40: 00, LPR_New, Error, 0, USPHND0088, LPR_New, (Work result). The work failed. The assignment was used in Appendix 14 (LPR_New_Job). The last step to start is step 1 (Download. Material), 00: 00: 00,0,0 ,, 0

11/04/2014 06: 40: 00, LPR_New, Error, 1, USPHND0088, LPR_New, Download Material, Run as user: nestle \ ussqldbserver .... 00.5324.00 for 32-bit Copyright (C) Microsoft Corp. 1984-2005. All rights reserved.
Started: 6:40:00 AM Error: 2014-04-11 06: 40: 00.39 Code: 0xC001700A Source: Description: The version number in the package is not valid. The version number cannot be greater than the current version number. Error complete error: 2014-04-11 06: 40: 00.39
Code: 0xC0016020 Source: Description: Transferring packages from version 3 to version 2 with error 0xC001700A "The version number in the package is invalid. The version number cannot be greater than the current version number.". Error completion error: 2014-04-11 06: 40: 00.39 Code: 0xC0010018 Source: Description: Error loading value "3" from node "DTS: Property". Completion error Failed to load package "\ usphnd0088 \ dataxfer \ LPR \ LPR New \ UploadMaterial.dtsx" becau ... Process exit code 5. Failed to complete step., 00: 00: 00,0,0 ,, 0

Answer 1

Have you checked which version of BIDS was created in the project file? This occurs when the version of the SQL Server Agent is different from the version used to build the project in which the SSIS package is located.

There is a proposal to rebuild the project in the correct version of BIDS, which corresponds to the server agent used to run the task. Another option is to specify the location / path to the DTEXEC file that you want to use (depending on the version you are using).

References : MSDN / Error migrating a package from version 3 to version 2 with error 0xC001700A. The version number in the package is not valid. The version number cannot be greater than the current version number .

Answer 2

On this blog: http://blogs.msdn.com/b/jason_howell/archive/2014/09/30/ssis-error-when-deploying-from-vs-2013-to-ssisdb-in-sql-2012. aspx

The main reason is that currently (September 2014) SSDT BI 2014 for Visual Studio 2013 does not support SSIS packages for SQL Server 2012.

This is a general feature request, and the product group is knowledgeable about the requirement.

http://connect.microsoft.com/SQLServer/feedbackdetail/view/944882/ssdt-bi-2014-backward-compatibility-for-ssis-2012

SSDT for VS 2013 currently only works with SQL Server 2014. You need to use SSDT-BI for Visual Studio 2012 with SQL Server 2012 SSISDB.

Answer 3

To provide a newer answer using SQL Server Data Tools 2015, you can set the target deployment version for your integration project to 2012, 2014 or 2016 (by default it is 2016 and will cause version number errors in DB 2012/2014 until you install its correct). I am successfully implementing SQL 2012 integration now with SSDT 2015 after installing on "SQL Server 2012".