Share via

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.

  • Article

I guess at least once every SQL developer might have come across this error on SQL Server 2008 while running a SQL job that calls a package.

Reason for the error: Old version of the DTEXEC is picked up by SQL Server instead of the new one. That means, the exe shipped with 2005 is picked up when it is expected to use the one shipped with 2008. So, obviously this happens when SQL Server 2008 is running along with SQL Server 2005 on the same machine. As a result of this, we end up with two versions of DTEXEC executables. One residing in SQL Server 2005 path ("C:\Program Files\Microsoft SQL Server\90\DTS\Binn") and the other in SQL Server 2008 path ("C:\Program Files\Microsoft SQL Server\100\DTS\Binn").

Fix for the error: There are three workarounds to correct this.

1. Hard code the path of SQL Server 2008's DTEXEC while calling the SSIS package as shown below.

C:\Program Files\Microsoft SQL Server\100\DTS\Binn\DTEXEC.exe /F "D:\MyFolder\MyPackage.dtsx"

2. Rename the old exe in the 2005 path to a different name (Example:- C:\Program Files\Microsoft SQL Server\90\DTS\Binn\DTEXEC_Old.exe)

3. Go to PATH environmental variable and edit it in such a way that "C:\Program Files\Microsoft SQL Server\100\DTS\Binn" path appears well before the "C:\Program Files\Microsoft SQL Server\90\DTS\Binn" path.

Please drop me a note if this has helped you.

Comments

  • Anonymous
    December 23, 2008
    PingBack from http://www.codedstyle.com/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/

  • Anonymous
    March 24, 2009
    The comment has been removed

  • Anonymous
    May 07, 2009
    Hello Ramoji!                   for its worked well thanks a ton for such a valued one.

  • Anonymous
    May 08, 2009
    Thanks a lot Ramoji! Renaming the old exe worked for us.....

  • Anonymous
    June 10, 2009
    Thank YOU! Renaming the file worked perfectly and my packages are now running error free once more.

  • Anonymous
    June 12, 2009
    Thank You. Renaming the file really works. And no more errors now.

  • Anonymous
    June 25, 2009
    The comment has been removed

  • Anonymous
    August 20, 2009
    Thanks a lot...This article was really very helpful...

  • Anonymous
    September 16, 2009
    If you're doing this programmatically, you just need to update the reference (Microsoft.SQLServer.ManagedDTS) in your project from the SQL Server 2005's to SQL Server 2008's.

  • Anonymous
    August 16, 2010
    Thant's a lot. I did this:

  1. Rename the old exe in the 2005 path to a different name (Example:- C:Program FilesMicrosoft SQL Server90DTSBinnDTEXEC_Old.exe) And works fine :)

  • Anonymous
    January 04, 2011
    thanks a lot  - quick knock out :)

  • Anonymous
    January 05, 2011
    VioLa.... Just renaming the ...../90/DTEXEC.exe   to something else  worked fine.  .. Thanx...

  • Anonymous
    February 24, 2011
    Worked - thank you - I renamed the old dtexec.exe.

  • Anonymous
    April 06, 2011
    I Renamed the C:Program FilesMicrosoft SQL Server90DTSBinnDTEXEC.exe to ...DTEXEC_old.exe... it worked for me.. Thank u very much...!!

  • Anonymous
    June 08, 2011
    Simple advice. Several options, all of them easy.  Million thanks.

  • Anonymous
    July 26, 2011
    Thanks a lot !!!!! Very Good Article

  • Anonymous
    December 09, 2011
    Attached is an example of what I used.  Hope this helps. c: cd program files cd microsoft sql server cd 100 cd dts cd binn dtexec.exe /FILE "\Your Package Location.dtsx"

  • Anonymous
    October 09, 2012
    Hi, I have a different situation here. I developed SSIS package with Lookup transformation in SQL Server 2008R2 but production server is SQL Server 2005. So while i am trying to create a job in production server (i.e. SQL server 2005) it is throwing an error( same as above). So i tried re develop SSIS package in SQL Server 2005 but i am not getting same kind of fuctionality for Lookup transformation ( there is no option of sending no match entries to no match putput). Is there any way i can use my 2008 R2 SSIS package in SQL server 2005. Help me Thanks.

  • Anonymous
    October 21, 2012
    Thanks ... It was really very helpful.

  • Anonymous
    December 10, 2012
    wow, such an awesome solution. Happened to me after an in-place upgrade from '05 to '08. Simply renaming the file worked.

  • Anonymous
    April 15, 2013
    Thanks. I could solve the version problem. However after that i am getting "   Description: To run a SSIS package outside of Business Intelligence Developm nt Studio you must install Standard Edition of Integration Services or higher. End Error " BIDS and Integration services for 2008 are installed. Still i am getting the above error.Can you suggest what needs to be done now ?

  • Anonymous
    October 28, 2013
    used C:program files option but had to put  double quotes to make it work. Great help! "C:Program FilesMicrosoft SQL Server100DTSBinnDTEXEC.exe" /F "D:MyFolderMyPackage.dtsx"

  • Anonymous
    November 19, 2013
    Thanks so much! Had a similar issue but with a different error code 0xC0011008. 2008 package wouldn't deploy using the manifest as I usually use 2005. Renamed the 2005 one and then back deployed and worked like a charm! Thanks!

  • Anonymous
    April 15, 2014
    I have created an SSIS package using MS SQL 2008 and calling from console application build in VS2008.......I am getting the following error while loading the package

  • Anonymous
    April 15, 2014
    The comment has been removed

  • Anonymous
    July 28, 2014
    Thanks this helped had the same error scheduling a dtsx package to run with task scheduler through a bat file. I had both 2008 R2 and 2010 installed. Once I removed 2008 works great.

  • Anonymous
    October 02, 2014
    tks i have faced this problem now running with our error you gave grate solution tks again

  • Anonymous
    March 03, 2015
    My package works in SQL Server Mge Studio. I am getting this error when trying to open the package in Visual Studio.  I need to change something in the package and cannot open it.

  • Anonymous
    August 03, 2015
    I hardcoded the path to the DTEXEC while calling the SSIS package as you mentioned and it worked for me.   Thank you so much!!!!

  • Anonymous
    January 12, 2016
    Hi..Can someone make me clear of 1st work around ( C:Program FilesMicrosoft SQL Server100DTSBinnDTEXEC.exe /F "D:MyFolderMyPackage.dtsx")