I'm running a dts (pre ssis) pkg under mgt studio/dts 2000 pkg
designer and am finding that unless I open each transform individually
(after opening pkg) prior to 1st execution, I get errors having
something to do with Data Pump Tasks requiring Transformations to be
specified. Does anybody recognize this behavior and know of a way to
avoid this?

Hi, it seems as the transformation between 2 data connections is not
defined. But as you say, the package runs correctly once open I guess
the transform is not saved or something prevents it to be saved or
tested.
How is the pkg stored (msdb or file)? How do you run the package? Did
you get the same error even if you run it with dtsrun.exe?
Which kind of connection are you dealing with? For example, is one of
the two a remote internet server?

M.

Hi, it seems as the transformation between 2 data connections is not
defined. But as you say, the package runs correctly once open I guess
the transform is not saved or something prevents it to be saved or
tested.
How is the pkg stored (msdb or file)? How do you run the package? Did
you get the same error even if you run it with dtsrun.exe?
Which kind of connection are you dealing with? For example, is one of
the two a remote internet server?

M.

Hi, it seems as the transformation between 2 data connections is not
defined. But as you say, the package runs correctly once open I guess
the transform is not saved or something prevents it to be saved or
tested.
How is the pkg stored (msdb or file)? How do you run the package? Did
you get the same error even if you run it with dtsrun.exe?
Which kind of connection are you dealing with? For example, is one of
the two a remote internet server?

M.

Hi, it seems as the transformation between 2 data connections is not
defined. But as you say, the package runs correctly once open I guess
the transform is not saved or something prevents it to be saved or
tested.
How is the pkg stored (msdb or file)? How do you run the package? Did
you get the same error even if you run it with dtsrun.exe?
Which kind of connection are you dealing with? For example, is one of
the two a remote internet server?

M.

Hi, it seems as the transformation between 2 data connections is not
defined. But as you say, the package runs correctly once open I guess
the transform is not saved or something prevents it to be saved or
tested.
How is the pkg stored (msdb or file)? How do you run the package? Did
you get the same error even if you run it with dtsrun.exe?
Which kind of connection are you dealing with? For example, is one of
the two a remote internet server?

M.

Hi, it seems as the transformation between 2 data connections is not
defined. But as you say, the package runs correctly once open I guess
the transform is not saved or something prevents it to be saved or
tested.
How is the pkg stored (msdb or file)? How do you run the package? Did
you get the same error even if you run it with dtsrun.exe?
Which kind of connection are you dealing with? For example, is one of
the two a remote internet server?

M.

Hi, it seems as the transformation between 2 data connections is not
defined. But as you say, the package runs correctly once open I guess
the transform is not saved or something prevents it to be saved or
tested.
How is the pkg stored (msdb or file)? How do you run the package? Did
you get the same error even if you run it with dtsrun.exe?
Which kind of connection are you dealing with? For example, is one of
the two a remote internet server?

M.

Hi, it seems as the transformation between 2 data connections is not
defined. But as you say, the package runs correctly once open I guess
the transform is not saved or something prevents it to be saved or
tested.
How is the pkg stored (msdb or file)? How do you run the package? Did
you get the same error even if you run it with dtsrun.exe?
Which kind of connection are you dealing with? For example, is one of
the two a remote internet server?

M.

On Sep 18, 4:01*am, matteus <matteog... (AT) gmail (DOT) com> wrote:
thanks matteus, package is stored in msdb, I run it in dts designer by
clicking the run button after opening pkg, since posting this question
I've learned that if I open and close every transform and then save, I
dont need to open and close all over again. This is painful for large
pkgs, and a bit challenging when all of the transforms arent
immediately discernable to the naked eye due to their proximity to
other transforms. So if you have a workaround, I'd love to hear it.
This seems a little crazy to me.