SSIS error: version number in the package is not valid

  • 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.

  • 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.

  • 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.

  • Hi,

    I've used this as a solution and it worked.

    ** When you are trying to create the SSIS package in VS 2015, make sure before you create the package to do the following:

    1) On the Prject Menu click on Properties (last option down the menu)

    2) Under Configuration Properties, click TargetServerVersion then on the drop down menu select SQL Server 2012

    3) Click Yes on the next message Screen

    4) Redeploy the package

    5) direct your schedule job to the new package

    6) Error message won't show again and the job will complete as expected.

    Thank you.;-)

    Yaz

  • yasser.najah 55931 - Thursday, November 10, 2016 1:40 PM

    Hi,I've used this as a solution and it worked.** When you are trying to create the SSIS package in VS 2015, make sure before you create the package to do the following:1) On the Prject Menu click on Properties (last option down the menu)2) Under Configuration Properties, click TargetServerVersion then on the drop down menu select SQL Server 20123) Click Yes on the next message Screen4) Redeploy the package5) direct your schedule job to the new package6) Error message won't show again and the job will complete as expected.Thank you.;-)

    Thank you - this really helped me!

Viewing 5 posts - 1 through 4 (of 4 total)

You must be logged in to reply to this topic. Login to reply