I have a SQL Server 2005 SSIS package that runs successfully in my local environment and also runs successfully in Development environment using SQL Agent(different DataSouce- using SetValues). However it Fails in Production. I get the following error: "VS_NEEDSNEWMETADATA". End Error Error: 2011-09-08 11:03:49.37 Code: 0xC004700C Source: Data Flow Task DTS.Pipeline Description: One or more component failed validation. End Error Error: 2011-09-08 11:03:49.37 Code: 0xC0024107 Source: Data Flow Task Description: There were errors during task validation. End Error DTExec: The package execution returned DTSER_FAILURE (1). Started: 11:03:38 AM Finished: 11:03:49 AM Elapsed: 11.265 seconds. The package execution failed. The step failed. I have tried what I felt were the obvious and not so obvious steps starting with the most obvious. I refreshed the metadata of the component by replacing the SQL Select with a basic Select * so that new data would be brought in. Then I pasted the statement back and refreshed the downstream tasks and the red(x’s) disappeared. (I also refreshed other sources to be safe). I then committed to my source control and re-imported my package back into the MSDB folder and my Job. This is what I tried next… I tried changing the owner of the package, package source, Run As properties…so that it pointed to a higher user, package source to PackageStore instead of SQLServer, and RunAs the MainUser instead of SQLServerAgentAccount. This (it seems) led me on a bit of a “wild goose chase”. So I’m at the end of the road as far as ideas. Not sure if this is a bizarre permissions issue. I would appreciate any feedback or thoughts. Thanks, Pete

Hi peterjustin311, Please make sure you are using correct package protection level. If we goes with the default package protection level ‘EncryptSenstiveWithUserKey’ then same package might not execute as expected in other environments because package was encrypted with user’s personal key. To make package execution smooth across environment, one has to first understand the package protection level property behaviour, please see http://msdn2.microsoft.com/en-us/library/microsoft.sqlserver.dts.runtime.dtsprotectionlevel.aspx . In general, to avoid most of the package deployment error from one system to another system, please set package protection level to ‘DontSaveSenstive’. Hope that helps. Thanks, Eileen Forum Support Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

A VS_NEEDSNEWMETADATA typically doesn't have anything to do with the package itself - it usually has to do with connections. In your case, is it possible that your production package is attempting to read data from locations that are not EXACTLY the same as you read from in development? Don't assume anything - make sure that the package is reading data from EXACTLY the same locations. If there are package configurations involved, review the SSIS logs to ensure they are being applied properly. Talk to me now on