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

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

Post by dmc » Sat, 15 Jan 2005 05:08:14


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' FALIS.

Any comments or suggestions is much appreciated.

TIA
DMC
 
 
 

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

Post by Sue Hoegem » Sat, 15 Jan 2005 05:44:18

It's hard to say without knowing what the error is when the
jobs fail.
When you right click the package and schedule it, it will
set the authentication and job owner based upon how the
person scheduling it has Enterprise Manager configured for
authentication. Generally when I've seen people hit this
issue, it's due issues related to that.
When you create the job yourself, you control the
authentication used by dtsrun and who owns the job. Creating
the jobs yourself is often easier to maintain and
troubleshoot as you can view the dtsrun command and aren't
dealing the issues that could be in the encrypted dtsrun
command you get when right clicking a package and scheduling
it from there.

-Sue

On Thu, 13 Jan 2005 15:08:14 -0500, "dmc"

 
 
 

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

Post by dmc » Sun, 16 Jan 2005 05:42:12

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.
 
 
 

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

Post by dmc » Sun, 16 Jan 2005 07:37:25

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
 
 
 

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

Post by Sue Hoegem » Sun, 16 Jan 2005 08:00:34

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"
 
 
 

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

Post by Steen Pers » Tue, 18 Jan 2005 19:10:47

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
S ***
 
 
 

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

Post by dmc » Tue, 18 Jan 2005 23:50:02

Hello,

Yes, that is the exact error message.

In fact, we created a very simple DTS package like reading the last entry
out of a particular table on our database and another one was mapping a
drive. Of course the DTS local package works and FAILS if we schedule it.

To make everything easy we made sure that the owner is a domain admin and
also a member of local administrators, allowed to start a service, is a dbo
and SA member, pretty much a "god" like account.

This is now becoming apparent, the part of the error message "The system
cannot find the file specified" we believe is talking about the encrypted
DTS file. Is there a key or hive within the registry that we can check?

TIA
DMC





file
dbo.
 
 
 

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

Post by dmc » Tue, 18 Jan 2005 23:51:31

Hello,

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

TIA
DMC



job
 
 
 

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

Post by dmc » Wed, 19 Jan 2005 07:18:11

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




file
dbo.