SSIS package Upgrade from 2005 to 2012

Question

Hi,

We have a Solution file with 8 projects for SSIS packages. All of them are in VSS. They all have been created in 2005. Now we installed VS 2012 and SSDT on our local machines. I got latest of solution and projects from VSS on new machine. I tried to open solution file which took me SSIS package Upgrade wizard. I followed the steps and in the last step of conversion, it displayed that it had errors. The errors are:

Error 0xc001f429: Package Upgrade: The file, "C:\SSIS\compay\hello.dtsx", could not be opened for writing. The file could be read-only, or you do not have the correct permissions.

and for some packages, it is like this:

Messages
 * Information 0x40019316: : The provider name for the connection manager "OLEDBConnection" has been changed from "SQLNCLI.1" to "SQLNCLI10".
 
 * Information 0x40019316: : The provider name for the connection manager "OLEDBConnection" has been changed from "SQLNCLI10" to "SQLNCLI11".
 
 * Information 0x40016019: : The package format was migrated from version 2 to version 6. It must be saved to retain migration changes.
 
 
 * Warning: PackageName: Found SQL Server Integration Services 2005 Script Task "ScriptTask_49664f73e0f440bbb0e7d44f01036bff" that requires migration!
 
 * Information 0x4001601a:PackageName: The Script Task "ScriptTask_49664f73e0f440bbb0e7d44f01036bff" has been migrated. The package must be saved to retain migration changes.
 
 * Error 0xc001f429: Package Upgrade: The file, "C:\SSIS\company\Hi.dtsx", could not be opened for writing. The file could be read-only, or you do not have the correct permissions.
 

But solution and all projects and packages show that they are checked out. I checked properties also. Read only checkbox is not checked. 

Please suggest what to do. I appreciate your response.

Thanks,

Answer 1

Are they checked out from VSS working folder or from your solution? Are both the paths the same?

---

Please Mark This As Answer if it helps to solve the issue Visakh ---------------------------- http://visakhm.blogspot.com/ https://www.facebook.com/VmBlogs

Answer 2

What I did is: Even solution is in VSS. I got latest version as writable copy to my local work station folder which is same as working folder in VSS. Then I went to explore and made all folders and files as writable by unchecking readonly check box. Then I double clicked on sln file which let to the wizard.

Answer 3

Why didnt you check it out directly from VSS rather than going this long route?  How would VSS now that file is in checked out status if you go and manually change readwrite property? I think it may be that its getting confused when you tried to save it into its working folder as it still has status as checked in and not locked by anyone.

Can you try saving packages copies to different folder and then do the upgrade by including them onto a IS project?

---

Please Mark This As Answer if it helps to solve the issue Visakh ---------------------------- http://visakhm.blogspot.com/ https://www.facebook.com/VmBlogs