Parameter Bindings migrating a Execute Package Task
Hi all, I'm facing a problem with a SSIS project migrated from SSIS 2005 to SSIS 2012. This project contains a main.dtsx that calls several dtsx child packages, but it seems that Execute Package Task doesn't propagate UserVariable from root package to child package. Googling, I've seen there can be problem using Execute Package Task with parameter inherited from root package and that I have to use Parameter Bindings, anyway I've tried to configure Parameter Bindings but I can't perform any action (Add button is always disabled) Can someone explain me how to solve the problem? Thank you in advance for your help. Best regards Fabrizio
May 31st, 2012 11:58am

Seems to work fine for me. Are you sure that you have a parameters defined in your child packages? (Switch to Parameters tab of package) You cannot map directly to a child variable. Chuck Pedretti | Magenic North Region | magenic.com
Free Windows Admin Tool Kit Click here and download it now
May 31st, 2012 2:34pm

For me it doesn't work but consider migration progress maintain package deployment model for me. With package deployment it seems Parameter bindings is always disabled. Is it correct? Is it possible to migrate a dtsx package that calls dtsx child packages maintaining package deployment after the migration? If Yes do we have to perform some actions on child package to inherit variables from root package or no action should be required? In our scenario it seems that variables are not inherited from root package to child package....is it possible? Thank you again for your help. Best regards Fabrizio
June 1st, 2012 3:51am

Parameters are only available in the new project deployment model. If you want a child package to inherit a variable value from the root package, you need to set-up a parent configuration.MCTS, MCITP - Please mark posts as answered where appropriate.
Free Windows Admin Tool Kit Click here and download it now
June 1st, 2012 4:50am

Thank you for your reply, I'm migrating several dtsx package from SSIS 2005 to SSIS 2012, my packages on old machine correctly took variables from root package in inherited pacakges. After the migration wizard it seems my child packages fail to retrieve variables from root package. Do I need to perform some additional steps to restore inheritance from root package to child package or it should be automatic? Thank you again for your help. Best regards Fabrizio
June 1st, 2012 5:08am

Well, since the newly migrated packages seem to fail to retrieve the variables, it seems you need to perform some additional steps :) I would check if the parent configurations are still in place and if the variables have the correct scope.MCTS, MCITP - Please mark posts as answered where appropriate.
Free Windows Admin Tool Kit Click here and download it now
June 1st, 2012 5:11am

Yes you're right :-) but I've double-checked the variables a lot of times and it seems (of course only it seems) there are no errors. For instance in my root package (MAIN) I have the following variable CARTELLA_IMP_SSIS In my child package I have a variable with the same name and looking at Package Configuration I can see the following assignment Configurazione 2 Parent package variable CARTELLA_IMP_SSIS CARTELLA_IMP_SSIS Value As far as I know this is the only check to perform to see if a child variable is linked to a parent package vartiable. Running the package in Debug (with a breakpoint on the first step of the child package) it seems that CARTELLA_IMP_SSIS variable contains the value specified in design time instead of the value that should be inherited from parent package. Could you help me to understand the problem? Best regards Fabrizio
June 1st, 2012 5:26am

If you run the packages in BIDS and the parent package configuration fails, there should be warning/informational message in the progress window or in the output window.MCTS, MCITP - Please mark posts as answered where appropriate.
Free Windows Admin Tool Kit Click here and download it now
June 1st, 2012 5:28am

Thank you for your reply, here you are the output of the execution (sorry for the long mail) I can see only one error Error: 0xC001404B at CLIENTI, Log provider "SSIS log provider for Text files": The SSIS logging provider has failed to open the log. Error code: 0x80070003. but log path value for child package CLIENTI is the result of the following expression: @[Utente::CARTELLA_IMP_SSIS] + "LOG\\LOG_CLIENTI.TXT" CARTELLA_IMP_SSIS is inherited from parent packaga and the value seems to be ok. Information: 0x40016041 at MAIN: The package is attempting to configure from the XML file "D:\SSIS\STORECARLI\Import.dtsConfig". SSIS package "D:\STOREITALIA\MAIN.dtsx" starting. Information: 0x40016041 at MAIN: The package is attempting to configure from the XML file "D:\SSIS\STORECARLI\Import.dtsConfig". Information: 0x4004300A at Genera LOG, SSIS.Pipeline: Validation phase is beginning. Information: 0x4004300A at Genera riepilogo, SSIS.Pipeline: Validation phase is beginning. Executing ExecutePackageTask: CLIENTI.DTSX Information: 0x40016042 at CLIENTI: The package is attempting to configure from the parent variable "CONN_STOREITALIA1". Information: 0x40016042 at CLIENTI: The package is attempting to configure from the parent variable "CARTELLA_IMP_SSIS". Information: 0x40016042 at CLIENTI: The package is attempting to configure from the parent variable "CARTELLA_STORICO". Information: 0x40016042 at CLIENTI: The package is attempting to configure from the parent variable "DATAORA". Information: 0x40016042 at CLIENTI: The package is attempting to configure from the parent variable "FILE_ANAGRAFICHE". Information: 0x4004300A at Importa in TMP_IMPORT, SSIS.Pipeline: Validation phase is beginning. Information: 0x4004300A at Produci File Posizioni, SSIS.Pipeline: Validation phase is beginning. Information: 0x4004300A at Sposta in tabelle temporanee, SSIS.Pipeline: Validation phase is beginning. Warning: 0x802092A7 at Sposta in tabelle temporanee, Destinazione TMP_PS_PROSPS [1658]: Truncation may occur due to inserting data from data flow column "FLAG_ALTRI_ACQ_WEB" with a length of 50 to database column "FLAG_ALTRI_ACQ_WEB" with a length of 1. Warning: 0x802092A7 at Sposta in tabelle temporanee, Destinazione TMP_PS_TELEFONI [1743]: Truncation may occur due to inserting data from data flow column "COD_PROSPECT" with a length of 50 to database column "COD_PROSPECT" with a length of 9. Warning: 0x802092A7 at Sposta in tabelle temporanee, Destinazione TMP_PS_TELEFONI [1743]: Truncation may occur due to inserting data from data flow column "TIPO_TEL" with a length of 50 to database column "TIPO_TEL" with a length of 1. Warning: 0x802092A7 at Sposta in tabelle temporanee, Destinazione TMP_PS_TELEFONI [1743]: Truncation may occur due to inserting data from data flow column "PREFISSO_TEL" with a length of 50 to database column "PREFISSO_TEL_INT" with a length of 4. Warning: 0x802092A7 at Sposta in tabelle temporanee, Destinazione TMP_PS_TELEFONI [1743]: Truncation may occur due to inserting data from data flow column "NUM_TEL" with a length of 50 to database column "NUM_TEL" with a length of 15. Error: 0xC001404B at CLIENTI, Log provider "SSIS log provider for Text files": The SSIS logging provider has failed to open the log. Error code: 0x80070003. The system cannot find the path specified. Information: 0x40016042 at CLIENTI: The package is attempting to configure from the parent variable "CONN_STOREITALIA1". Information: 0x40016042 at CLIENTI: The package is attempting to configure from the parent variable "CARTELLA_IMP_SSIS". Information: 0x40016042 at CLIENTI: The package is attempting to configure from the parent variable "CARTELLA_STORICO". Information: 0x40016042 at CLIENTI: The package is attempting to configure from the parent variable "DATAORA". Information: 0x40016042 at CLIENTI: The package is attempting to configure from the parent variable "FILE_ANAGRAFICHE". Information: 0x4004300A at Importa in TMP_IMPORT, SSIS.Pipeline: Validation phase is beginning. Information: 0x4004300A at Produci File Posizioni, SSIS.Pipeline: Validation phase is beginning. Information: 0x4004300A at Sposta in tabelle temporanee, SSIS.Pipeline: Validation phase is beginning. Warning: 0x802092A7 at Sposta in tabelle temporanee, Destinazione TMP_PS_TELEFONI [1743]: Truncation may occur due to inserting data from data flow column "COD_PROSPECT" with a length of 50 to database column "COD_PROSPECT" with a length of 9. Warning: 0x802092A7 at Sposta in tabelle temporanee, Destinazione TMP_PS_TELEFONI [1743]: Truncation may occur due to inserting data from data flow column "TIPO_TEL" with a length of 50 to database column "TIPO_TEL" with a length of 1. Warning: 0x802092A7 at Sposta in tabelle temporanee, Destinazione TMP_PS_TELEFONI [1743]: Truncation may occur due to inserting data from data flow column "PREFISSO_TEL" with a length of 50 to database column "PREFISSO_TEL_INT" with a length of 4. Warning: 0x802092A7 at Sposta in tabelle temporanee, Destinazione TMP_PS_TELEFONI [1743]: Truncation may occur due to inserting data from data flow column "NUM_TEL" with a length of 50 to database column "NUM_TEL" with a length of 15. Error: 0xC001404B at CLIENTI, Log provider "SSIS log provider for Text files": The SSIS logging provider has failed to open the log. Error code: 0x80070003. The system cannot find the path specified. Warning: 0x80019002 at SSIS - CLIENTI: SSIS Warning Code DTS_W_MAXIMUMERRORCOUNTREACHED. The Execution method succeeded, but the number of errors raised (2) reached the maximum allowed (1); resulting in failure. This occurs when the number of errors reaches the number specified in MaximumErrorCount. Change the MaximumErrorCount or fix the errors. Task failed: SSIS - CLIENTI Warning: 0x80019002 at MAIN: SSIS Warning Code DTS_W_MAXIMUMERRORCOUNTREACHED. The Execution method succeeded, but the number of errors raised (2) reached the maximum allowed (1); resulting in failure. This occurs when the number of errors reaches the number specified in MaximumErrorCount. Change the MaximumErrorCount or fix the errors. SSIS package "D:\STOREITALIA\MAIN.dtsx" finished: Failure.
June 1st, 2012 6:03am

Perhaps I've found the problem. The problem is related to log provider for child packages. Each child package has a log provider, the path is configured using a parent package variable, it seems this variable isn't available at package validation but is configured after validation phase. This lead to error in package execution. Replacing parent package variable with specific package variable fix the error. Thank you all for the help. Best regards Fabrizio
Free Windows Admin Tool Kit Click here and download it now
June 1st, 2012 11:06am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics