Hi,

In a project I work on we provide various exports to our users via DTS
packages
that are called using a stored procedure.

Recently a new package was added that does nothing but run 27 of the other
packages
one after the other.

This works fine on test servers and for several of the companys that use our
product.
However one of our clients is getting a SQL Server access denied error on
the first
child package being executed (DTSStep_DTSExecutePackageTask_1). The strange
thing is that they can run all the child packages individual without error,
it is only
when they run the parent that contains them that it goes wrong.

All the 27 child packages use the same global variables. Therefore the
parent that
runs them all has the same global variables set-up and I have setup the
mapping
for them in the Execute Package tasks Outer Package Global Variables.

Any ideas as to how I might go about debugging this?

Regards,
Peter

I get the same error using a stored proc to run DTS. What I am finding
is that the servername i.e. server1\instance1 gets truncated to server1
hence all parameterized connections fail. If you execute the same
command from the command prompt passing the global variable for the
servername it works.

I call the package execute from another DTS package using execute SQL
task to run the stored procedure.

If anyone can throw light on this I would appreciate it.

*** Sent via Developersdex http://www.developersdex.com ***

Peter,

Does this package have owner password and are you passing variables to it?
If it does and you are passing variables, are you passing the password
before calling the package?

Ilya

"Peter Row" <get.lost (AT) spammers (DOT) com> wrote