Task Scheduler Keeps Stopping

[Mark MacGregor]

I'm running into a problem where the task scheduler
stops working. Nothing tells me that it's not working
other than I observe that the given task has not run when
it was supposed to run. For example, I can use the wizard
to create a new task to open notepad and tell it to run
automatically in a couple of minutes. When the time
rolls, it doesn't start.

When I go to my computer, manage, and check the service,
it says it's running. As soon as I click "restart" the
service, then I get message that some tasks did not
complete because task scheduler was not running. Then
everything works for a while. I can run the above notepad
test and it starts when it's supposed to. But later on
(after I'm not sure how long, maybe a day, maybe hours) it
stops working again. This is insidious because there is
no indication that the scheduler has stopped working.

I use remote desktop a lot, in case that might have
something to do with it. I'm running as an administrator
with passwords and all of that set up. The notepad test I
described above should be a good indication that the
scheduler has actually stopped for some reason other than
what I have seen discussed so far in these forums.

Any help on where to start? Knowledge base was not
helpful -- no similar problem could be found. Thanks.

Mark

 

[Guest]

I have noticed the same phenomena. Many a times scheduler does not run after setting it up for a schedule. The only thing I have noticed is that any time a scheduled task is opened to review its settings, even if to view without any changes, I must always reset the password before closing. Otherwise it does not run thereafter.

 

[Guest]

The key point I found for getting scheduled tasks to run is that you must set the user account password. So your user account must have a password for logging in every time you boot-up and log into your user account. When you create a scheduled task, the user account password must be set for that task to run. The user account must have admin priveliges also.

 

[Mark MacGregor]

Yes, all of these things are true in my case. As I said,
it runs properly right after I restart the service, but
stops some time after that. What a pain! The thing is, I
am using this to perform backups, so it's really important!

-----Original Message-----
The key point I found for getting scheduled tasks to run

is that you must set the user account password. So your
user account must have a password for logging in every
time you boot-up and log into your user account. When you
create a scheduled task, the user account password must be
set for that task to run. The user account must have
admin priveliges also.

 

[Guest]

Yes, this has happened to me also and it puzzles me too.
The only other thing I can think of and have tried is
on the SETTINGS Tab, the check box "Stop the task if it runs for xx hours."
I believe it defaults to 72 hours. I have set mine to 3 or 4 hours. I recently increased the time to 9 hours.
But, perhaps its better to leave it at 72 hours?
I'm thinking if you do not turn on the computer, or for some other reason
the task cannot run during that timeout period, the task aborts?

 

[Guest]

Disregard my last suggestion -
Further testing revealed that "Stop the task if it runs for xx hours"
will terminate the scheduled app Only After it has Started in the first place.