I've been battling this for a long time. I have a package built with 2008 with a script task. The script task is set to run under .Net framework 3.5 (project properties inside the script task code). This package will not run on a server with 2012 installed (under the legacy integration services service). Actually, it does run if I execute the package from my local machine (pointing to the server), but it won't run directly on the server; it gives:
The component metadata for “Script Component, clsid {874F7595-FB5F-4OFF-9BAF-FBFF825OE3EF}” could not be upgraded to the newer version of the component. The PerformUpgrade method failed.
Creating a new 2012 style package and using the same code in a script component works fine.
It seems like maybe the old SSIS service is not able to run my script using the proper framework or something, but there's no way of knowing. Is this scenario simply not going to work?