Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

Child package won't run from within Parent in an execute package task Expand / Collapse
Author
Message
Posted Tuesday, June 2, 2009 10:05 AM
SSC Veteran

SSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC Veteran

Group: General Forum Members
Last Login: Thursday, October 23, 2014 7:06 AM
Points: 247, Visits: 703
I've created and deployed a package on to a server that populates a data warehouse for me. However, I want to build another more complex package that relies on the data warehouse data being up to date before completing it's main tasks. I thought I could run the deployed package from the deployed File System package ensuring it will always be run before getting to the correct processing.

The deployed package is working fine at present on its own. When running it from an execute package task in my new "parent package" it fails giving the following error:


Error: Error 0xC0012050 while loading package file "\\gdt-sql02\e$\Program Files\SL Client Transfer\CopyClientFile.dtsx". Package failed validation from the ExecutePackage task. The package cannot run. .

In debug mode, this opens the child package when you run it for some reason. Looking at the execution results for the child package it looks like it fails on the password/username used in the data reader source (see start of error below):


[DataReader Source [1]] Error: System.Data.Odbc.OdbcException: ERROR [28000] [Sybase][ODBC Driver][SQL Anywhere]Invalid user ID or password ERROR [28000] [Sybase][ODBC Driver][SQL Anywhere]Invalid user ID or password at System.Data.Odbc.OdbcConnection.HandleError(OdbcHandle hrHandle, RetCode retcode) at System.Data.Odbc.OdbcConnectionHandle..c


I don't know why there's a password issue here as, according to a few postings I've seen, it states you should leave the Password field as it was in the execute package task editor unless you set a password against the child package, which I haven't done.

On opening the original package (the child) in BIDS, or by running the package from SQL Agent, this has now stopped working as well. Not sure whether the parent child package has corrupted the deployed package.

Any ideas anyone?
Post #727556
Posted Wednesday, June 3, 2009 3:55 AM
Old Hand

Old HandOld HandOld HandOld HandOld HandOld HandOld HandOld Hand

Group: General Forum Members
Last Login: Tuesday, May 27, 2014 9:38 AM
Points: 380, Visits: 176
How have you configured the child package?

One of the limitations of calling the child package from the parent package using the Execute Package Task is that you can't specify configuration values for the child package.

Have you tried the Execute Process Task, using the DTEXEC command to execute the package? This task gives you the ability to specify an argument for the package and list the configuration files required to run the package.
Post #728020
Posted Wednesday, June 3, 2009 4:20 AM
SSC Veteran

SSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC Veteran

Group: General Forum Members
Last Login: Thursday, October 23, 2014 7:06 AM
Points: 247, Visits: 703
Haven't used a configuration file for the child package actually. With the child package not working either, I'm thinking it may have something to do with that package instead. Problem is I don't know why it's stopped working as a result of adding it in as an execute package in the parent. I would have thought the original development version wouldn't be touched.
Post #728035
Posted Friday, June 5, 2009 8:29 AM
SSC Veteran

SSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC Veteran

Group: General Forum Members
Last Login: Thursday, October 23, 2014 7:06 AM
Points: 247, Visits: 703
Anyone have any ideas on this or have come across a similar issue?
Post #729769
Posted Friday, June 5, 2009 8:51 AM


SSC Veteran

SSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC Veteran

Group: General Forum Members
Last Login: Wednesday, November 19, 2014 7:18 AM
Points: 251, Visits: 1,758
Do I have it right that the originally deployed package fails in BIDS or in SQL agent, but it will still run successfully via dtexec? If so, are all of the run methods using the same user credentials?

I've not seen a case where a parent package has corrupted a child package before. Have you verified that there are no permission or network issues that are affecting your obdc connection?
Post #729799
Posted Friday, June 5, 2009 10:11 AM
SSC Veteran

SSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC Veteran

Group: General Forum Members
Last Login: Thursday, October 23, 2014 7:06 AM
Points: 247, Visits: 703
I'm still trying the execute package solution rather than moved on to running it in dtexec. It fails in BIDS, but I have a sql agent job that runs the deployed package and that's stopped working now as well, which is a bit more critical as the team I support rely on that one. The SQL Agent job runs as a different user but uses the same dsn connection setup.

I can test the odbc dsn connection in admin tools data sources (ODBC) and it connects. I also set up a test package in BIDS to connect to the same data source and that connects fine, so it's a mystery why my other two packages don't work (child on its own, and parent running child).
Post #729876
Posted Friday, June 5, 2009 11:26 AM


SSC Veteran

SSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC Veteran

Group: General Forum Members
Last Login: Wednesday, November 19, 2014 7:18 AM
Points: 251, Visits: 1,758
When the SQL Agent job fails, is it throwing the same odbc error as when it fails in BIDS? Are there any events in your server error log that might indicate an authorization failure?

Sorry, but I'm not sure why it's giving you the grief that it is, I'm just trying to run through all of the steps that I would if it were happening to me. None of my connections use odbc, they're all OLE DB or ADO.NET.
Post #729931
Posted Monday, June 8, 2009 4:46 AM
SSC Veteran

SSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC Veteran

Group: General Forum Members
Last Login: Thursday, October 23, 2014 7:06 AM
Points: 247, Visits: 703
Yes, the same authorisation error I have in BIDS.

It's the ADO.NET connection I've used here. It's New ADO.NET connection > .Net Providers\Odbc Data Provider connection.
Post #730580
Posted Tuesday, June 9, 2009 9:32 AM
SSC Veteran

SSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC Veteran

Group: General Forum Members
Last Login: Thursday, October 23, 2014 7:06 AM
Points: 247, Visits: 703
Worked out what this was in the end. I had set up the Ado.net connection in the connection manager area and it kept on losing the password for the odbc connection. Setting up a data source in the solution explorer window seems to have retained the password. Seems a bug to me.
Post #731559
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse