Hi all,

I am trying to schedule a DTS package which does some
deletion, insertion and updating in a DB2 database. It
always fails. However, when I run the package stand alone
it works fine. My SQL Server agent is started and using
the correct service account (other jobs process when run
strictly against my own SQL Server). Does anyone have any
ideas?

Thanks,

Mark

What is the error you are getting when it fails? When you execute a
DTS package manually, it executes from your PC and under your security
context. When scheduled as a job, it executes from the server and
under the security context of SQL Agent if the job is owned by a
sysadmin. The issues when scheduling packages generally fall within
the difference between what's configured and how on your PC and your
security vs. SQL Agent.

-Sue

On Wed, 2 Jun 2004 15:45:57 -0700, "Mark Frank"
<mark.a.frank (AT) wellsfargo (DOT) com> wrote:

Hi Sue,

The error I get is below:

Executed as user: AD-ENT\franmara. The process could not be created for
step 1 of job 0x2C97A06FD2ADD440B45404CC4A033E71 (reason: The system
cannot find the file specified). The step failed.


*** Sent via Devdex http://www.devdex.com ***
Don't just participate in USENET...get rewarded for it!

And what did you install and configure on the SQL Server for access to
DB2?

-Sue

On Thu, 03 Jun 2004 09:50:07 -0700, Mark Frank
<mark.a.frank (AT) wellsfargo (DOT) com> wrote:

I have DB2 client installed on my machine and have tried using both an
ODBC system DSN and the native DB2 OLE Driver.

Does that help?

Thanks,

Mark

*** Sent via Devdex http://www.devdex.com ***
Don't just participate in USENET...get rewarded for it!

Yes...if your machine is where SQL Server resides.
When you run the package, it looks like it doesn't think the
components are installed or it can't find the path to some
of the components.
If your machine is where SQL Server is installed then try
logging into your machine using the service account you are
using for the SQL Agent. And then try reinstalling the DB2
client. Then test the package by executing it while logged
in as the service account.
If your machine is not where SQL Server is installed, log
onto the SQL Server box using the service account. Install
the DB2 client software. Test while logged in as the service
account.

-Sue

On Thu, 03 Jun 2004 16:17:06 -0700, Mark Frank
<mark.a.frank (AT) wellsfargo (DOT) com> wrote: