I have moved some DTS packages to a new server. I am calling a
package from within an outer package. In the outer package (package
3)I am setting the server through a global variable and setting the
GUID through a query

select id from sysdtspackages where name = 'package 2'

This appears to be working. However, package3 calls package2 and
package2 calls package1. In this package2 that calls package1, I'm
setting the server and the GUID in the same way that I am above. And
when run alone, package2 works just fine. BUT, when package 3 calls
package2, the query that sets the GUIDS for the package1's is not ever
working. In other words, the outer most package finds the middle
package and tries to run it, but the middle package cannot find the
innermost package. It gives me an error that the PackageID does not
exist. It appears that the set Guid dynamic properties task is never
even being executed in the middle package. Can someone help me?
Thanks!

In message <ce695524.0402041356.7c2678a1 (AT) posting (DOT) google.com>, Sara
<sara2thebradley (AT) yahoo (DOT) com> writes
The theory sounds fine, and passing parameters between packages is also
something that works well for me, so I'm not entirely sure what the
cause is, however I there are two things you might try-

Can you execute package 2 on it's own, not from package 3, and does it
execute package 1 OK?

Why not remove the package Guids entirely? Unless you want a specific
version just use the name. If you have issues with deployment when Guids
change then just blank the task property.

Make the Execute Package Task name dependent only
(http://www.sqldts.com/default.aspx?216)

--
Darren Green (SQL Server MVP)
DTS - http://www.sqldts.com

PASS - the definitive, global community for SQL Server professionals
http://www.sqlpass.org

Thanks Darren. Yes, package 2 executes just fine on it's own. It's
when package 3 calls it that it has trouble setting the GUIDS within
package 2. I went to the disconnected edit feature of the package
menu within package 2, as well as within the package 1's that package
2 calls, and I cannot delete the PackageID. The property for this
will not allow me to edit the PackageID. I'm not sure why.


Darren Green <darren.green (AT) reply-to-newsgroup-sqldts (DOT) com> wrote

I finally got this to work by setting up a dynamic properties task to
use a global variable that sets the PackageIDs for all of the execute
package tasks in package 2 and package 3 to nothing. Not to <not
displayable>, but to nothing. This alone did not work, but then I set
up outer package global variables in the outer package (package 3) and
the inner package (package 2) to that global variable whose value was
nothing. This passed the empty packageID to the innermost package
(package 1) and life is good!


Darren Green <darren.green (AT) reply-to-newsgroup-sqldts (DOT) com> wrote