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 ] Error: System.Data.Odbc.OdbcException: ERROR  [Sybase][ODBC Driver][SQL Anywhere]Invalid user ID or password ERROR  [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?