Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase 12»»

Downgrade SSIS 2008 package to 2005 Expand / Collapse
Author
Message
Posted Wednesday, January 12, 2011 1:40 AM
SSC-Addicted

SSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-Addicted

Group: General Forum Members
Last Login: Monday, November 17, 2014 7:32 AM
Points: 412, Visits: 1,412
I developed and tested 3 .dtsx packages in my development environment using Visual Studio 2008 v9.0.30729.4462 QFE, not realising that the servers these packages should be run on are still SQL server 2005. How do I make these packages created using Visual Studio 2008 with SQL Server Integration Services installed run on SQL server 2005 ?

The error messages I get when trying to execute the packages on SQL 2005 are:
The version number in the package is not valid. The version number cannot be greater than current version number.

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

Error loading value "<DTS:Property xmlns:DTS="www.microsoft.com/SqlServer/Dts" DTS:Name="PackageFormatVersion">3</DTS:Property>" from node "DTS:Property".

The servers can not be upgraded to SQL 2008, so I need a way to get my packages saved in a format acceptable for SQL 2005.

Thanks a lot.




Posting Data Etiquette - Jeff Moden
Posting Performance Based Questions - Gail Shaw
Hidden RBAR - Jeff Moden
Cross Tabs and Pivots - Jeff Moden
Catch-all queries - Gail Shaw


If you don't have time to do it right, when will you have time to do it over?
Post #1046316
Posted Wednesday, January 12, 2011 1:49 AM


SSCertifiable

SSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiable

Group: General Forum Members
Last Login: Today @ 2:31 AM
Points: 5,317, Visits: 12,358
I am afraid that there is no way of doing this other than manually recreating the packages in 2005.


Help us to help you. For better, quicker and more-focused answers to your questions, consider following the advice in this link.

When you ask a question (and please do ask a question: "My T-SQL does not work" just doesn't cut it), please provide enough information for us to understand its context.

It is better to keep your mouth shut and appear stupid than to open it and remove all doubt. (Mark Twain)
Post #1046319
Posted Wednesday, January 12, 2011 2:08 AM


Ten Centuries

Ten CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen Centuries

Group: General Forum Members
Last Login: Wednesday, December 10, 2014 10:49 AM
Points: 1,201, Visits: 791
2008 does not support backward compatability, so you can do this. You need to do the re work using visual studio 2005.
Post #1046325
Posted Wednesday, January 12, 2011 5:47 AM
SSC-Addicted

SSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-Addicted

Group: General Forum Members
Last Login: Monday, November 17, 2014 7:32 AM
Points: 412, Visits: 1,412
Thanks for your responses. I managed to downgrade the packages. I need to thank a colleague -with great Google skills- for this, who sent me this link that references a little application SSISdowngrade on CodePlex doing most of the work downgrading a 2008 .dtsx package to 2005.

After running my packages through this application I could still not open the packages. So I opened up the packages in an xml editor and removed all references to system variable "System::ProductVersion", which apparently is not known in 2005. Plus I changed the connection string to my SQL database to use "SQLNCLI.1" for the Provider instead of "SQLNCLI10.1".

After doing this I could succesfully open the .dtsx files in Visual Studio 2005 / SQL server 2005. Only the encryption of the ftp password was still reported as an error, but that was easily solved by opening the package in Visual Studion 2005 and setting a new password.

Thank you Jasmin for saving my day.




Posting Data Etiquette - Jeff Moden
Posting Performance Based Questions - Gail Shaw
Hidden RBAR - Jeff Moden
Cross Tabs and Pivots - Jeff Moden
Catch-all queries - Gail Shaw


If you don't have time to do it right, when will you have time to do it over?
Post #1046420
Posted Wednesday, January 12, 2011 5:52 AM


SSCertifiable

SSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiable

Group: General Forum Members
Last Login: Today @ 2:31 AM
Points: 5,317, Visits: 12,358
Thanks for posting back - I'd never heard of that.


Help us to help you. For better, quicker and more-focused answers to your questions, consider following the advice in this link.

When you ask a question (and please do ask a question: "My T-SQL does not work" just doesn't cut it), please provide enough information for us to understand its context.

It is better to keep your mouth shut and appear stupid than to open it and remove all doubt. (Mark Twain)
Post #1046426
Posted Wednesday, January 12, 2011 7:51 AM


SSChampion

SSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampion

Group: General Forum Members
Last Login: 2 days ago @ 6:46 AM
Points: 13,646, Visits: 11,524
R.P.Rozema (1/12/2011)
Thanks for your responses. I managed to downgrade the packages. I need to thank a colleague -with great Google skills- for this, who sent me this link that references a little application SSISdowngrade on CodePlex doing most of the work downgrading a 2008 .dtsx package to 2005.

After running my packages through this application I could still not open the packages. So I opened up the packages in an xml editor and removed all references to system variable "System::ProductVersion", which apparently is not known in 2005. Plus I changed the connection string to my SQL database to use "SQLNCLI.1" for the Provider instead of "SQLNCLI10.1".

After doing this I could succesfully open the .dtsx files in Visual Studio 2005 / SQL server 2005. Only the encryption of the ftp password was still reported as an error, but that was easily solved by opening the package in Visual Studion 2005 and setting a new password.


I wonder what the Downgrade tool does, since you still had to manually intervene for the ProductVersion and edit the connectionstrings.




How to post forum questions.
Need an answer? No, you need a question.
What’s the deal with Excel & SSIS?

Member of LinkedIn. My blog at LessThanDot.

MCSA SQL Server 2012 - MCSE Business Intelligence
Post #1046491
Posted Wednesday, January 12, 2011 8:00 AM


SSCertifiable

SSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiable

Group: General Forum Members
Last Login: Today @ 2:31 AM
Points: 5,317, Visits: 12,358
I wonder what the Downgrade tool does, since you still had to manually intervene for the ProductVersion and edit the connectionstrings.


Sounds to me like a self-nomination for a mini research project in your spare time



Help us to help you. For better, quicker and more-focused answers to your questions, consider following the advice in this link.

When you ask a question (and please do ask a question: "My T-SQL does not work" just doesn't cut it), please provide enough information for us to understand its context.

It is better to keep your mouth shut and appear stupid than to open it and remove all doubt. (Mark Twain)
Post #1046501
Posted Wednesday, January 12, 2011 11:32 AM


SSChampion

SSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampion

Group: General Forum Members
Last Login: 2 days ago @ 6:46 AM
Points: 13,646, Visits: 11,524
Phil Parkin (1/12/2011)
I wonder what the Downgrade tool does, since you still had to manually intervene for the ProductVersion and edit the connectionstrings.


Sounds to me like a self-nomination for a mini research project in your spare time


Hehe.

No.





How to post forum questions.
Need an answer? No, you need a question.
What’s the deal with Excel & SSIS?

Member of LinkedIn. My blog at LessThanDot.

MCSA SQL Server 2012 - MCSE Business Intelligence
Post #1046673
Posted Wednesday, January 12, 2011 11:19 PM
SSC-Addicted

SSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-Addicted

Group: General Forum Members
Last Login: Monday, November 17, 2014 7:32 AM
Points: 412, Visits: 1,412
Source code is available on codeplex, so you can see for yourself what it does. I don't care I had to do some things manually, I am still very thankful to the author. (S)he correctly saw that more people ran into the same issue and shared her/his knowledge.



Posting Data Etiquette - Jeff Moden
Posting Performance Based Questions - Gail Shaw
Hidden RBAR - Jeff Moden
Cross Tabs and Pivots - Jeff Moden
Catch-all queries - Gail Shaw


If you don't have time to do it right, when will you have time to do it over?
Post #1047016
Posted Friday, October 28, 2011 1:50 PM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Tuesday, October 8, 2013 12:20 AM
Points: 1, Visits: 49
A big THANK YOU to the downgrade application author!
Post #1197656
« Prev Topic | Next Topic »

Add to briefcase 12»»

Permissions Expand / Collapse