|
|
Scheduled tasks dont work but look like they are
Hi All,
We are having intermittent problems with Windows Task Scheduler.
Two scenarios:
1. Everything will work fine for a few weeks, then suddenly tasks that used
to work ok will complete as normal, but task scheduler does not know they are
finished, and so the tasks status sits as running.. even though the program
and executable have closed and gone away.. this stops future instances of the
scheduled task from running.
2. Tasks that are scheduled to run, and have run for weeks without issue,
suddenly just stop running. They sit waiting for their scheduled start time,
the start time elapses, but they continue to sit there and do not enter the
running state.
This happens across a number of servers, all of the Windows 2003, some are
32 bit, some are 64 bit and some are R2 while others are not..
Does anyone know why task scheduler might behave so erratically?
Cheers!
|
|
0
|
|
|
|
Reply
|
Utf
|
1/18/2010 5:55:01 AM |
|
"Luke" <Luke@discussions.microsoft.com> said this in news item
news:48EC3EE2-129A-40FB-B03A-0D8456ABACD1@microsoft.com...
> Hi All,
> We are having intermittent problems with Windows Task Scheduler.
>
> Two scenarios:
> 1. Everything will work fine for a few weeks, then suddenly tasks that
> used
> to work ok will complete as normal, but task scheduler does not know they
> are
> finished, and so the tasks status sits as running.. even though the
> program
> and executable have closed and gone away.. this stops future instances of
> the
> scheduled task from running.
>
> 2. Tasks that are scheduled to run, and have run for weeks without issue,
> suddenly just stop running. They sit waiting for their scheduled start
> time,
> the start time elapses, but they continue to sit there and do not enter
> the
> running state.
>
> This happens across a number of servers, all of the Windows 2003, some are
> 32 bit, some are 64 bit and some are R2 while others are not..
>
> Does anyone know why task scheduler might behave so erratically?
>
> Cheers!
Let's have a look at one of your tasks that behaves eratically (i.e. the
exact command line that it runs).
|
|
0
|
|
|
|
Reply
|
Pegasus
|
1/18/2010 7:00:11 AM
|
|
|
1 Replies
251 Views
(page loaded in 0.048 seconds)
|
|
|
|
|
|
|
|
|