December 30, 2010 at 11:41 pm
I have two packages A and B
A calls B internally
EG:
A -- task1, task2, Execute B, task 4....
The tasks run fine upto task2 but give the above error when it reaches to execute package B
Also, package B uses parent variables
I have the dtsconfig file for package A which I assume is working fine, since the first 2 tasks in package A are running without problems. Package B also has a password. (Encrypted package)
Both packages are stored in C:\Program Files\Microsoft SQL Server\100\DTS\Packages
and I can view them in stored packages in File system when I connect to the servers Integration services in management Studio.
Where am I going wrong? 🙁 🙁
Thanks.
December 31, 2010 at 2:50 am
Got it!!!
It was looking for package B in the SQL server (One dropdown option for a Package task) as its location.
(and not the file system)
So Putting them in the dts/packages folder was not necessary.
So I imported them to MSDB folder in the Stored packages option which I get on connecting to SSIS from Management studio. When importing, make sure you are using the Import from "File system" and then browse to the dtsx file and include it (package B in my case)
All works fine now.
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply