Re: Jobs Failed do not work when scheduled done via DTS Scheduled Package
From: dmc (dario_at_semiconductor.com)
Date: 01/17/05
- Next message: David: "Re: Numbers of DB in SQL"
- Previous message: David Portas: "Re: Numbers of DB in SQL"
- In reply to: Sue Hoegemeier: "Re: Jobs Failed do not work when scheduled done via DTS Scheduled Package"
- Messages sorted by: [ date ] [ thread ]
Date: Mon, 17 Jan 2005 17:18:11 -0500
hello,
the answer was very simple. If you type set within the DOS prompt it will
show you all the variable settings including the PATH. During the
installation I remember that the setup asked where do I want to put the data
and where do I want the executables. Well, I put EXE on C: and then DATA on
H: and of course never thought that this would haunt me down the road. For
some weird reason when I typed set I didn't find any path or information
about the SQL. Maybe the last software that I installed on the server took
the SQL info out within the PATH.
I edited the PATH and only told the system about the SQL on C: and tried
running one of the Jobs and it executed without a hitch. It was a lucky
guess I suppose since most of the tips were talking about permission. Oh
well...
Cheers,
DMC
"Sue Hoegemeier" <Sue_H@nomail.please> wrote in message
news:66jgu05vr5pake5le7115695liqttlbvrm@4ax.com...
> Is that the exact error message you get for all of the jobs
> that fail - system cannot find the file specified?
> What does the DTS package do? Does it involve linked
> servers, does it access files or resources on the network?
> And more importantly who owns the jobs that get created?
> When you schedule these packages using the right click,
> schedule package, the account used is whatever account you
> have used to register Enterprise Manager. What account is
> that?
> I understand that you can manually create jobs and get the
> packages to run so your issue isn't the typical problem that
> comes from a package that runs manually but not when
> scheduled. The only real difference with the manually
> creating the job and using the schedule package
> functionality is that you can control what login and who
> owns the job when you manually create the job. That's why
> you'd really want to double check those things.
>
> -Sue
>
> On Fri, 14 Jan 2005 15:42:12 -0500, "dmc"
> <dario@semiconductor.com> wrote:
>
> >first of all, thank you for your reply.
> >
> >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.
> >
> >thanks.
> >
>
- Next message: David: "Re: Numbers of DB in SQL"
- Previous message: David Portas: "Re: Numbers of DB in SQL"
- In reply to: Sue Hoegemeier: "Re: Jobs Failed do not work when scheduled done via DTS Scheduled Package"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
