November 18, 2011 at 12:02 pm
Hi guys,
I've got the following problem I cannot figure out:
I have an SSIS package (let's call it SSIS_child) with a database connection and 2 variables (ServerName and DatabaseName).
The database connection has 'Expressions' set where InitialCatalog is mapped to 'DatabaseName' variable, and ServerName is mapped to 'ServerName' variable. I set the values of these variables and run the package and it works with no problems.
Since I want this SSIS_child to run as one of the components of a larger package, I created a 2nd package (let's call it SSIS_parent). This package also has 2 variables (ServerName and DatabaseName). All this SSIS does is call SSIS_child, passing the variable values from parent package to the child package (this is achieved by enabling package configurations of SSIS_child and adding these 2 variables with configuration type 'Parent package variable').
I now run SSIS_parent, which is supposed to just take the variable values, pass them to SSIS_child and then run the package. The run fails with the following message:
"Error: Error 0xC0012050 while loading package file "C:\SSIS_CHILD.dtsx". Package failed validation from the ExecutePackage task. The package cannot run."
.
Please advise as I don't see what the problem could be.
Thank you!
November 18, 2011 at 12:30 pm
sql_er (11/18/2011)
I now run SSIS_parent, which is supposed to just take the variable values, pass them to SSIS_child and then run the package. The run fails with the following message:"Error: Error 0xC0012050 while loading package file "C:\SSIS_CHILD.dtsx". Package failed validation from the ExecutePackage task. The package cannot run."
That is most probably the last message of the stack - search the whole log looking for "Error" messages before error 0xC0012050
Long shot? if child package runs fine when called individually and fails when called from Parent package then I would check parent package, it may be calling child package in an inapropriate way - connectivity strings would be my first suspect.
_____________________________________
Pablo (Paul) Berzukov
Author of Understanding Database Administration available at Amazon and other bookstores.
Disclaimer: Advice is provided to the best of my knowledge but no implicit or explicit warranties are provided. Since the advisor explicitly encourages testing any and all suggestions on a test non-production environment advisor should not held liable or responsible for any actions taken based on the given advice.November 18, 2011 at 1:57 pm
PaulB,
Thank you for the suggestion.
I actually found this link, and it seemed a lot of people had similar problems: http://social.msdn.microsoft.com/forums/en-US/sqlintegrationservices/thread/43c84491-66f8-4a61-bd97-54a824d56be7/
For me, all I had to do was recreate the parent package and it worked.
I'm not sure what is stored internally in SSIS, but it is not the 1st time I had to re-create the package and it just worked, even though it was identical (visually) to the package that did not.
Thanks!
Viewing 3 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply