March 12, 2008 at 5:45 am
Please help. Posted yesterday and today on SSIS board, but no answers.
I have a connection string for a child package defined as:
@[User::CRDirectory] + @[User:ackageCRSisdomDrive] (sorry about the emoticon - read colonP instead)
Each of these variables is blank in the parent package, and populated by a config file at run time
There are 3 config files. CRDirectory is specified in the config file listed first in the agent job, and PackageCRSisdomDrive is in the second config.
CRDirectory is given the value:
E:\Mirror_Files\DEV\GOODIES\COMMON ROUTINES\
PackageCRSisdomDrive is given the value:
CR_Sisdom_Drive.dtsx
The error message from the job is:
Error 0x80070003 while loading package file "E:\Mirror_Files\DEV\GOODIES\COMMON ROUTINES\". The system cannot find the path specified.
The command line in the job is:
/FILE "E:\Mirror_Files\DEV\SOLUTIONS\Daily_Tower_Data_Quality\Daily_Tower_DQ_Parent_Pkg.dtsx" /DECRYPT /CONFIGFILE "E:\Mirror_Files\DEV\GOODIES\DEV_Environment.dtsConfig" /CONFIGFILE "E:\Mirror_Files\DEV\SOLUTIONS\Daily_Tower_Data_Quality\DEV_Daily_Tower_DQ.dtsConfig" /CONFIGFILE "E:\Mirror_Files\DEV\SOLUTIONS\Daily_Tower_Data_Quality\DEV_DTS.dtsConfig" /MAXCONCURRENT " -1 " /CHECKPOINTING OFF /REPORTING E
I've checked and re-checked all the obvious things like spelling mistakes.
Before adding this child package to the front of the job there were connection strings for 3 other child packages that all worked, but the complete string was being held in a single variable
The only thing I can think of, is that the package isn't added into the project. I didn't want to do this as it creates a copy in the directory the rest of the project is in. The package will be a common routine called by a number of jobs, and I don't want spurious versions kicking around.
Any ideas, anyone?
TIA
March 12, 2008 at 7:19 am
If I were you I would add the package to the project as a test. You can always remove it later, and cleanup the directory the project is in. I would try that just as a test to rule that out. Did you post all of the config files?? It looked as though there was one missing.
March 12, 2008 at 8:06 am
Thank you for your response mmenser.
I've actually just managed to get it to work, without bringing the common package into the project.
I didn't post all 3 config files because there was nothing in the bottom level one to affect the problem I was having.
I had been using a scheduled job to test it, to save me keying in the fully qualified paths for all the files, using dtexec. I had tried using dtexec yesterday but got a mass of confusing errrors (that I now believe to be a result of a typing error in what was a long string).
How I sorted the problem was to use dtexec, and to set the active directory to the location of the parent package, which was where 2 of the config files were also located. I first ran the package without any config, and then with the first config only. Each time the errors made sense in respect of the missing parameters.
On the third go I added in the second config file and immediately saw it was unreadable. I had created it using Notepad, and it is the largest of the 3 config files. When I opened it in BIDS I eventually spotted a mis-spelt tag, nowhere near the variable declarations that had been giving me a problem.
Having corrected that, the job completed successfully
March 12, 2008 at 8:14 am
Awesome!
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply