Task Scheduler

  • Thread starter Thread starter LarryIn MI
  • Start date Start date
L

LarryIn MI

We have a customer running WIN200 Professional.
The following happened:

Win 2000 - no service packs
Scheduled an eodjob on Friday night to run.
EodJob Executed okay.
Saturday AM a scheduled tapebackup failed.
Saturday and Sunday nights the eodjob failed to run.

Win 2000 updated with SP4 early Monday
Eodjob again running at night.

Problem
The EODJOB used to run and open a window during the
running.
Now the EODJOB runs as though the logged in user is not
the run as user in the EODJOB (silent mode)

We have:
Deleted the EODJOB and recreated it.
Changed the Run as to Administrator
Logged in a Administrator

Still no change.

We have the EODJOB running on other 2000 computers just
fine.

It appears that MSTASK thinks the run as and the logged in
user are not the same, thus running the EODJOB in silent
mode.

Any ideas will be appreciated.

Thanks, in advance

Larry
 
What does Scheduled Tasks|Advanced|View Log have to say about it?

--
Regards,

Dave Patrick ....Please no email replies - reply in newsgroup.
Microsoft MVP [Windows NT/2000 Operating Systems]
http://www.microsoft.com/protect.

:
| We have a customer running WIN200 Professional.
| The following happened:
|
| Win 2000 - no service packs
| Scheduled an eodjob on Friday night to run.
| EodJob Executed okay.
| Saturday AM a scheduled tapebackup failed.
| Saturday and Sunday nights the eodjob failed to run.
|
| Win 2000 updated with SP4 early Monday
| Eodjob again running at night.
|
| Problem
| The EODJOB used to run and open a window during the
| running.
| Now the EODJOB runs as though the logged in user is not
| the run as user in the EODJOB (silent mode)
|
| We have:
| Deleted the EODJOB and recreated it.
| Changed the Run as to Administrator
| Logged in a Administrator
|
| Still no change.
|
| We have the EODJOB running on other 2000 computers just
| fine.
|
| It appears that MSTASK thinks the run as and the logged in
| user are not the same, thus running the EODJOB in silent
| mode.
|
| Any ideas will be appreciated.
|
| Thanks, in advance
|
| Larry
|
|
|
|
|
 
Here's a paste of the log

"NITESCHEDULE.job" (NITESCHEDULE.BAT)
Started 1/2/2004 10:21:26 PM
"NITESCHEDULE.job" (NITESCHEDULE.BAT)
Finished 1/2/2004 10:49:18 PM
Result: The task completed with an exit code of
(0).
-----Original Message-----
What does Scheduled Tasks|Advanced|View Log have to say about it?

--
Regards,

Dave Patrick ....Please no email replies - reply in newsgroup.
Microsoft MVP [Windows NT/2000 Operating Systems]
http://www.microsoft.com/protect.

:
| We have a customer running WIN200 Professional.
| The following happened:
|
| Win 2000 - no service packs
| Scheduled an eodjob on Friday night to run.
| EodJob Executed okay.
| Saturday AM a scheduled tapebackup failed.
| Saturday and Sunday nights the eodjob failed to run.
|
| Win 2000 updated with SP4 early Monday
| Eodjob again running at night.
|
| Problem
| The EODJOB used to run and open a window during the
| running.
| Now the EODJOB runs as though the logged in user is not
| the run as user in the EODJOB (silent mode)
|
| We have:
| Deleted the EODJOB and recreated it.
| Changed the Run as to Administrator
| Logged in a Administrator
|
| Still no change.
|
| We have the EODJOB running on other 2000 computers just
| fine.
|
| It appears that MSTASK thinks the run as and the logged in
| user are not the same, thus running the EODJOB in silent
| mode.
|
| Any ideas will be appreciated.
|
| Thanks, in advance
|
| Larry
|
|
|
|
|


.
Click to expand...
 
Then your problem lies elsewhere. Looks like Task Scheduler performed it's
function.

--
Regards,

Dave Patrick ....Please no email replies - reply in newsgroup.
Microsoft MVP [Windows NT/2000 Operating Systems]
http://www.microsoft.com/protect.

| Here's a paste of the log
|
| >>
|
| "NITESCHEDULE.job" (NITESCHEDULE.BAT)
| Started 1/2/2004 10:21:26 PM
| "NITESCHEDULE.job" (NITESCHEDULE.BAT)
| Finished 1/2/2004 10:49:18 PM
| Result: The task completed with an exit code of
| (0).
 
Back
Top