Scheduler not kicking out

  • Thread starter Thread starter Sandra
  • Start date Start date
S

Sandra

I'm using the scheduler app in Windows 2000 to trigger programs that run
every half hour. These have been working for a while but stopped kicking out
this morning. In Scheduler it says they did and if I manully select Run it
says they ran but they don't.
Anyone ever seen this?
 
It seems not a problem with Task Scheduler but a problem with the string on
the task's Run line.

--
Regards,

Dave Patrick ....Please no email replies - reply in newsgroup.
Microsoft Certified Professional
Microsoft MVP [Windows]
http://www.microsoft.com/protect

:
| I'm using the scheduler app in Windows 2000 to trigger programs that run
| every half hour. These have been working for a while but stopped kicking
out
| this morning. In Scheduler it says they did and if I manully select Run it
| says they ran but they don't.
| Anyone ever seen this?
|
|
 
Sandra said:
I'm using the scheduler app in Windows 2000 to trigger programs that run
every half hour. These have been working for a while but stopped kicking out
this morning. In Scheduler it says they did and if I manully select Run it
says they ran but they don't.
Anyone ever seen this?
Click to expand...

After a time change (DST), this problem is common to all Win2k partitions
that use Fat32. You will need to reset passwords within the Mstask GUI once for
each username that appears.

If you have 100 Jobs spreadout as 40 for user1, 30 for user2, 20 for user3, and
10 for user4 (total 100), you only need to reset passwords 4 times -- pick one
Job out of each set.
 
But these have been kicking out every day for weeks and DST was 4 days ago.
Is there a delay likethat before the problem kicks in?

If so, I'm not clear on the fix. I don't know what you mean by Mstask GUI.
Am I resetting domain passwords??

Thanks




Sandra said:
I'm using the scheduler app in Windows 2000 to trigger programs that run
every half hour. These have been working for a while but stopped kicking out
this morning. In Scheduler it says they did and if I manully select Run it
says they ran but they don't.
Anyone ever seen this?
Click to expand...

After a time change (DST), this problem is common to all Win2k partitions
that use Fat32. You will need to reset passwords within the Mstask GUI once
for
each username that appears.

If you have 100 Jobs spreadout as 40 for user1, 30 for user2, 20 for user3,
and
10 for user4 (total 100), you only need to reset passwords 4 times -- pick
one
Job out of each set.
 
I opened up the Scheduler properties and re-typed the password of the user.
No change. The things still won't kick out. If I click on them in Scheduler
and right click/rnu - nothing happens except scheduler shows they've run at
that time but they didn't.
AAAHHHHHH!!!!!



Sandra said:
I'm using the scheduler app in Windows 2000 to trigger programs that run
every half hour. These have been working for a while but stopped kicking out
this morning. In Scheduler it says they did and if I manully select Run it
says they ran but they don't.
Anyone ever seen this?
Click to expand...

After a time change (DST), this problem is common to all Win2k partitions
that use Fat32. You will need to reset passwords within the Mstask GUI once
for
each username that appears.

If you have 100 Jobs spreadout as 40 for user1, 30 for user2, 20 for user3,
and
10 for user4 (total 100), you only need to reset passwords 4 times -- pick
one
Job out of each set.
 
You might believe that the task did not run but perhaps
it did. Embed it in a batch file like so, then have a closer
look at its two log files:

@echo off
echo %date% %time% Start of task > c:\test.log
echo User=%UserName%, Path=%path% >> c:\test.log
c:\Tools\YourTask.exe 1>>c:\test.log 2>c:\test.err
echo ErrorLevel of c:\Tools\YourTask.exe=%ErrorLevel% >> c:\test.log
echo %date% %time% End of task >> c:\test.log
 
Back
Top