Parent Package Configuration Problems
Hi All, I moved my packages from Develop Environment to Different environment. I have three packages. one is Main, child and Sub-child packages. For all packages OLEDB connection manager value is getting from Variable. For Main package this variable is configured in Indirect XML file. For child package it is getting from Parent package variable and same way to sub Child package also. When I execute main package through Agent the sub child package is Raising Error event (while initialising package It is trying to connect with default connection value in the variable and raising Error event and the package is running fine with configured value only it is raising error event. Below are the error information. SSIS Error Code DTS_E_OLEDBERROR. An OLE DB error has occurred. Error code: 0x80004005. An OLE DB record is available. Source: "Microsoft SQL Server Native Client 10.0" Hresult: 0x80004005 Description: "Login failed for user 'MyMachine\SQLService'.". An OLE DB record is available. Source: "Microsoft SQL Server Native Client 10.0" Hresult: 0x80004005 Description: "Cannot open database "TestDataBase" requested by the login. The login failed.". SSIS Error Code DTS_E_CANNOTACQUIRECONNECTIONFROMCONNECTIONMANAGER. The AcquireConnection method call to the connection manager "LocalHost.TestDataBase" failed with error code 0xC0202009. There may be error messages posted before this with more information on why the AcquireConnection method call failed. In the sub child package I have given "TestDataBase" as default value. When deployment i have changed the Dtabase name.
May 7th, 2012 9:00am

it is probably because SQL Server Agent service account has not access to the database which is reffered in SSIS package, create a proxy account in this way and run the package with proxy account in sql server job: http://www.sqlservercentral.com/articles/Integration+Services+%28SSIS%29/69441/http://www.rad.pasfu.com
Free Windows Admin Tool Kit Click here and download it now
May 7th, 2012 9:12am

for a quick test you can ... 1- add a script task in all packages for all of them set the next steps 2-pass the connection variable to the script task 3- in the script task use a MsgBox to display the value something like Dim Message As String = Dts.Variables("uVar_SQLServerName").ToString Message = "Master Package SQL variable = " & Message MsgBox(Message) this will help you to see what values they have once they have been fired off NOTE: NEVER use message box ,this is just for testing , after testing delete all test Script tasks Thsi will help you to see if you have passed the right values from one package to another. Question: how are you calling your packages?? and how are you setting the variables from one package to another? Sincerely SH -- MCITP , MCTS -- Please kindly mark the post(s) that answered your question and/or vote for the post(s).
May 7th, 2012 9:17am

Thanks For your Reply.. The testDatabase is given when i developed my package. but actual value coming from Parent package. Here my problem is before getting the value from parent package the child package is validating the connection manager with existing values and raising an error event. After raised the event, package executed successfully with the new value coming form parent package. its only logging an error in the sysssislog table and package executed successfully. For connection manager i set delayvalidation property set to TRUE.
Free Windows Admin Tool Kit Click here and download it now
May 7th, 2012 9:19am

......the child package is validating the connection manager with existing values and raising an error event. Click on the connection manager and check the property , set the DelayValidation = TRUE then testSincerely SH -- MCITP , MCTS -- Please kindly mark the post(s) that answered your question and/or vote for the post(s).
May 7th, 2012 9:23am

I set dalay validation ture for Connection manager and even package level also. But still the package is raising Error Event..
Free Windows Admin Tool Kit Click here and download it now
May 7th, 2012 9:26am

Hi M Anil, Please check the account you are using to run the package in SQL Server Agent, it seems that the user "MyMachine\SQLService" have no permission to access the database "TestDataBase". Thanks, Eileen
May 14th, 2012 4:30am

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

Other recent topics Other recent topics