February 3, 2010 at 9:08 am
I hope this is the right forum to post this and find an answer.
I have several SSIS packages that have been created over the past couple of years. They were originally created using BIDS -- Visual Studio 2005 with Service Pack 1 installed.
I now have a new machine that has had Visual Studio 2005 Service Pack 2 installed and some, not all, of my package solutions will not open. I try to open the solution file (i.e. package.sln) and I get the following error: "The selected file is not a valid solution file"
Some of the packages are small and can be easily re-created, but a couple of the packages are extremely large and will take much time to re-do.
Does anyone know if there is a way to fix something so I can get into these files?
Thanks!
mj
~mj
February 3, 2010 at 10:11 am
Are you using VSS?
http://www.opcg.com/index.php/2009/03/17/visual-studio-the-selected-file-is-not-a-2005?blog=2
For better, quicker answers on T-SQL questions, click on the following...
http://www.sqlservercentral.com/articles/Best+Practices/61537/
For better answers on performance questions, click on the following...
http://www.sqlservercentral.com/articles/SQLServerCentral/66909/
February 3, 2010 at 10:51 am
Wow do I feel small! I figured this out finally (after a couple weeks of trying).
This was permission related on our server. Not only did I get a new machine, I've been moved to a new Domain and the folder that stores our SSIS packages needed to have the share permissions updated to reflect the Domain changes for users.
Once the permissions were corrected, I was able to open my packages again.
So many things to consider! lol
Hopefully this will help someone else at some point in time. 😀
~mj
Viewing 3 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply