Click here to monitor SSC
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

SSIS error: version number in the package is not valid Expand / Collapse
Author
Message
Posted Friday, February 22, 2013 9:48 AM
SSC-Enthusiastic

SSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-Enthusiastic

Group: General Forum Members
Last Login: Tuesday, May 3, 2016 9:55 PM
Points: 103, Visits: 328
I installed SSIS 2008 (SSIS, SSRS, SSAS....not the database engine) on a server that already had SQL Server 2005 installed that also had SSIS/SSRS.

I used BIDS 2008 to create an SSIS package, opened up SSMS 2008 which looks at the 2005 server engine to add/schedule a Job in the Agent to launch the SSIS 2008 package. I'm guessing this won't work because it's a SQL Server 2005 instance? Or is there a way to force the SQL Server Agent job use the C:\Program Files\Microsoft SQL Server\100\DTS\Binn\DTExec.exe instead of the one here...C:\Program Files\Microsoft SQL Server\90\DTS\Binn\DTExec.exe ???

The error I'm getting when I run the package is...

Execute Package Utility Version 9.00.5000.00 for 32-bit Copyright (C) Microsoft Corp 1984-2005. All rights reserved. Started: 8:55:33 AM Error: 2013-02-22 08:55:34.03 Code: 0xC001700A Source: Description: The version number in the package is not valid. The version number cannot be greater than current version number. End Error Error: 2013-02-22 08:55:34.03 Code: 0xC0016020 Source: Description: Package migration from version 3 to version 2 failed with error 0xC001700A "The version number in the package is not valid. The version number cannot be greater than current version number.". End Error Error: 2013-02-22 08:55:34.03 Code: 0xC0010018 Source: Description: Error loading value "<DTS:Property xmlns:DTS="www.microsoft.com/SqlServer/Dts" DTS:Name="PackageFormatVersion">3</DTS:Property>" from node "DTS:Property". End Error Could not load package "E:\2008\logixhealth\logix.dtsx" because of error 0xC0. The step failed.
Post #1423138
Posted Tuesday, February 26, 2013 3:58 PM
Ten Centuries

Ten CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen Centuries

Group: General Forum Members
Last Login: Wednesday, June 29, 2016 3:47 PM
Points: 1,200, Visits: 1,177
Edit the job step and choose operating system (cmdExec) instead of SQL Server Integration Services Package. Then set your command line to something like this:

C:\Program Files\Microsoft SQL Server\100\DTS\Binn\DTExec.exe /F "c:\packagepath\packagename.dtsx"

Your package must be saved in the filesystem in order to do this.
Post #1424271
Posted Thursday, February 11, 2016 4:28 PM
SSChasing Mays

SSChasing MaysSSChasing MaysSSChasing MaysSSChasing MaysSSChasing MaysSSChasing MaysSSChasing MaysSSChasing Mays

Group: General Forum Members
Last Login: Monday, September 19, 2016 3:42 PM
Points: 625, Visits: 1,942
Yes, this is old, but here's an answer for anyone finding this thread who is in the situation I was in...

I got this error stating it could not upgrade from version 8 to version 6. But I know for a fact I had edited the package in the SQL2012 Version of SQL Data Tools, I uploaded it to a SQL2012 SSIS instance, it ran successfully from a SQL2012 test SSIS Server I uploaded it to a few weeks ago, and when I open the DTSX file in notepad is clearly said
 <DTS:Property
DTS:Name="PackageFormatVersion">6</DTS:Property>

THE PROBLEM:

I installed SSMS 2014 last week, which I used to upload the dtsx file to SSISDB. Apparently, SSMS upgrades lower versions of dtsx files, or at least changes the PackageFormatVersion attribute.

THE SOLUTION:

Upload the dtsx file using the version of SSMS that matches the SSIS instance. When installing newer versions of SSMS, keep the old one on your workstation for tasks where SSMS is not backward compatible.



Post #1760662
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse