Re: Jobs Failed do not work when scheduled done via DTS Scheduled Package

From: dmc (dario_at_semiconductor.com)
Date: 01/17/05 

Date: Mon, 17 Jan 2005 09:51:31 -0500

Hello,

We are running it from the server itself (looged on locally) and not
remotely.

TIA
DMC

"Steen Persson" <SPE@REMOVEdatea.dk> wrote in message
news:u3cqRzH$EHA.3472@TK2MSFTNGP14.phx.gbl...
> Are you running the job from Enterprise Manager/QA on you local PC or via
> EM/QA directly on the server (e.g. via RemoteDesktop)? Depending on the
job
> steps you are running it might fail if you try to run it from your local
> machine -e.g if it involves any files or filepaths that is "known" by the
> server, but not by your local machine.
>
> Regards
> Steen
>
>
> dmc wrote:
> > Hi there,
> >
> > We found this problem a little odd, jobs that were created using DTS'
> > Scheduled Package FAILS all the time but if we create a new job
> > manually and use TSQL under steps it WORKS.
> >
> > Anything that was done via DTS' FAILS.
> >
> > here is a typical error that we get:
> >
> > The process could not be created for step 1 of job
> > 0x52C39FD0D0DE644E8750519DD6824E94 (reason: The system cannot find
> > the file specified). The step failed.
> >
> > the account that is logged on is a domain account and we even made it
> > a dbo. the sql is set to use either sql or windows authentication.
> >
> > It really looks like the Jobs are failing because the dtsrun doesn't
> > know where to find the file involved. Could be the SQL path got
> > screwed up or something? Do we need to check variable settings?
> >
> > Any comments or suggestions is much appreciated.
> >
> > TIA
> > dmc
>
>

Relevant Pages