Hi, I have a Master package and a few child packages deployed on the same server. I have run the packages successfully many times. But today when i redeployed the Packages, I am getting error while calling one the child package. Error: Error 0xC0012050 while preparing to load the package. Package failed validation from the ExecutePackage task. The package cannot run. While the other child packages are being called successfully, its quite strange the the process if failing for one child package. The settings for all the child packages are same in the Master Package. I am calling the Master Packge through SQL Agent Job. Any sugggestions please Regards Yuktah

If you are 100% certain that the child package is not corrupt, I would suggest deleting it out of the MSDB database and re-importing it.Todd C - MSCTS SQL Server 2005, MCITP BI Dev 2008 Please mark posts as answered where appropriate.

I have only deployment rights, I cant delete it from MSDB database :PRegards Yuktah

Sure you didn't forget to turn on the package to use package configuration file before deployment?Please mark the post as answered if it answers your question

The issue is definitely with the package validation. Make sure that configuration data is set correctly i.e. all servers mentioned in the connection strings exist and you do have access to those servers, no table schema or file format changes have occurred since the last successful run.http://btsbee.wordpress.com/

Elaborating above post from DotNetMaster,are you sure you parent package is successfully able to connect to the child package? Please note, the error occured before the child package got loaded to "Execute Package Task" so check you child package config on Production.Also try to see if there are detailed log generated for the same, that would give you clear info about error.

I have found out the issue and trying to figure out a solution. The issue is due to one of the Parent package variable in the Child Package. Here's wht hppnd. The Parent package is passing connection string ( E.g Connection A which points to Server A) to child package in Variable X. In the child Package, Connection A is set dynamically using expression which picks up the value present in Variable X. Now one of our developer changed Variable X value in the Child Package to point to Server B according to the requiremnt. Also the Parent Package is now passing connection string for Server B. When i redeployed the Master Package with this Child Package and the other Child Packages, it's only failing for this Child Package. If i remove the Variable X from the Child Package's Package Configuration, the Child Package is executed successfully. Now this is quite strange because whatever value is present in the Child Package Variable X should be overwritten by the value passed from the parent package. Is this some Metadata Issue? I recreated the Parent Package variable but it was of no use.Regards Yuktah

It is something to do with the way variables are mapped to child package. Check if the X variable in Child package is properly mapped to the connection string property of required Connection Manager.Please mark the post as answered if it answers your question

Hi, Everything is set properly. After more analysis, I found out a new thing. In one of the DFT Task, the oledb Source transformation was changed. Earlier Data Access Mode was a Table and now a SQL query is being used. Now if i change the Data Access mode to Table, the Child Package is called successfully. I will drop and recreate the OLEDB task and see how it'll work. Will post soon. Regards Yuktah

Hi, Well the issue has been resolved. After so much of analysis, the reason found was quite petty. Since one of the developer made changes in OLEDB Source to use Query to fetch data, some new tables were created in Dev environment. The same when deployed in the QA, the new tables were not created and as a result the Child Package was called but failed in validation itself. Even though the reason here was a fault from our end, what I am thinking is, the error returned by SSIS was not specific. The error did tell it was a validation error but not specifically at which point it was ocurring. Please correct me if i am wrong here.Regards Yuktah