October 9, 2013 at 8:30 am
I recently upgraded my SSMS 2008 to 2008 R2 to allow me to view SSIS packages through Integration Services. Since the upgrade, I have been unable to open any SSIS modules through BIDS on Visual Studio 2005 - the same version in which the packages were created. I get the following error:
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.".
I have seen similar topics on this issue, all relating to getting this error when running the packages and all the solutions seem to revolve around opening the package in the VS 2005 and saving as a 2005 package. Since I can not even open these packages, does anyone have any suggestions for getting around this error?
October 9, 2013 at 8:36 am
Are the packages stored in msdb or in the file system? Have you tried opening them with Visual Studio 2008?
John
October 9, 2013 at 8:47 am
They are stored in the file system. I don't have Visual Studio 2008 available (SQL Server 2008, but not VS 2008), so I am not able to use it to open the package.
October 9, 2013 at 8:49 am
But you upgraded to SSMS R2 using the installation DVD, right? You should be able to install Visual Studio (BIDS) from there.
John
October 9, 2013 at 8:55 am
I'll have to check. The install was done from a file share and I don't have complete access to the location (the joys of working for a large company that locks down EVERYTHING that might be helpful to a developer 😉 ). I don't remember seeing BIDS as an option to either include or ignore during the installation.
October 9, 2013 at 9:03 am
No, it will have been under something like Development Tools. It'll be documented somewhere.
John
October 10, 2013 at 1:02 pm
I poked around a little and found that I did have BIDS for 2008. I was able to open & update packages, after some playing around with the conversion wizard.
Thanks for your help in trouble-shooting!
Viewing 7 posts - 1 through 6 (of 6 total)
You must be logged in to reply to this topic. Login to reply