I have encountered this situation a number of times and wanted to see if
anyone else has run into it.

I have a few packages that primarily call other packages they are kinda a
loader package. I create this new "loader" package and add one or more
"Execute Package Task" to the designer. As I add the task I provide a
description and name the server then pick the package. I am careful not to
pick a particular version of a package just the top package name. As time
goes by I move this loader package to the testing or production environment.

When I move the package I open the loader package double click the task and
change the server name (If this sounds like way more work than should be
required I agree), once the server name has been changed it clears the
contents of the Package Name and it's GUID. I then reselect the package (not
simply paste the package name) from the test or production server.

Here is where I occasionally get an error. When the package executes it
errors and says the file was not found and the file it's trying to find is
the DTS package file... weird. When I go to select the package the GUID is
different. I reselect the package again and it works.

The frequency is low but quite the show stopper.

Any thoughts?

In message <12EBBF97-F173-4E3B-A062-DFAEBCA7687D (AT) microsoft (DOT) com>, LP
<LP (AT) discussions (DOT) microsoft.com> writes
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

That's GREAT!!!

It's tucked away in kinda of an out of the way place but, FANTASTIC!!!

Thanks very much.

"Darren Green" wrote: