Scheduled jobs don't run


R

rmo555

I schedule my AV to scan at 1:00am - but it doesn't start. My PC is ON
and the power settings are set so the monitor goes off after 20 minutes
of non use - but the hard drive is set to always be on and hibernate
and sleep are set to never. Can anyone tell my what else might be
stopping my AV from running?
 
Ad

Advertisements

P

Pegasus [MVP]

I schedule my AV to scan at 1:00am - but it doesn't start. My PC is ON
and the power settings are set so the monitor goes off after 20 minutes
of non use - but the hard drive is set to always be on and hibernate
and sleep are set to never. Can anyone tell my what else might be
stopping my AV from running?

What command line can you see in the Task Scheduler for this job?
 
J

Jose

I schedule my AV to scan at 1:00am - but it doesn't start.  My PC is ON
and the power settings are set so the monitor goes off after 20 minutes
of non use - but the hard drive is set to always be on and hibernate
and sleep are set to never.  Can anyone tell my what else might be
stopping my AV from running?

Is this a new Task?

Has it ever worked?

Did you create this task yourself or did some program create it for
you?

Some applications you may want to schedule at a conventient time
require
user intervention (answering questions) if something comes up or even
to get
started.

If you run it manually, does it ask you any questions needing an
input?

If it is your AV, what will it do if it runs into something? Ask you
what to do
(and you are not there)?

Does your application have command line options to run unattended?

What is your AV - maybe somebody knows or can research how to make
it run as a Task.

Not so popular advice from me to troubleshoot STs:

It is strongly suggested that the task be assigned to a user that has
a password (not the Administrator), so create a new user with a
password just for tasks or add a password to your account if needed.
You can temporarily assign yourself a PW to test and worry about
getting rid of it. Just get it working for now.

If you don't use an account with a password, you will get an error
trying to create the task. It will still be created, but will not
run
properly.

There is a way around this, but get this working first to be sure
your
mechanism is not afflicted.

Stop the Task Scheduler service.

Delete or rename the probably cluttered ST log file:

c:\windows\schedlgu.txt

Restart the Task Scheduler service to create a new log.

Browse to the c:\windows\tasks folder to see all your tasks. The
Next Run Time and Last Run Time columns are of interest.

Choose to Add Scheduled Task. Create a new task to run Command
Prompt
once, now. If you don't have a PW, you will get an error trying to
create it (more on that later). It will still be created, but will
never run.

Right click the new Command Prompts task and choose Run and a command
window should open immediately. If not, something is wrong. If yes,
your mechanism is sound. Look in the log file to see your results.

You know how to remove the log now, so that is up to you. Be sure
the
Task Scheduler service is running again.

Try to Run your troublesome task, observe the columns, and the log.

If your task fails to run manually, the errors in the log file are
the
clues to what to do next.
 
Ad

Advertisements

R

rmo555

Is this a new Task?

Has it ever worked?

Did you create this task yourself or did some program create it for
you?

Some applications you may want to schedule at a conventient time
require
user intervention (answering questions) if something comes up or even
to get
started.

If you run it manually, does it ask you any questions needing an
input?

If it is your AV, what will it do if it runs into something? Ask you
what to do
(and you are not there)?

Does your application have command line options to run unattended?

What is your AV - maybe somebody knows or can research how to make
it run as a Task.

Not so popular advice from me to troubleshoot STs:

It is strongly suggested that the task be assigned to a user that has
a password (not the Administrator), so create a new user with a
password just for tasks or add a password to your account if needed.
You can temporarily assign yourself a PW to test and worry about
getting rid of it. Just get it working for now.

If you don't use an account with a password, you will get an error
trying to create the task. It will still be created, but will not
run
properly.

There is a way around this, but get this working first to be sure
your
mechanism is not afflicted.

Stop the Task Scheduler service.

Delete or rename the probably cluttered ST log file:

c:\windows\schedlgu.txt

Restart the Task Scheduler service to create a new log.

Browse to the c:\windows\tasks folder to see all your tasks. The
Next Run Time and Last Run Time columns are of interest.

Choose to Add Scheduled Task. Create a new task to run Command
Prompt
once, now. If you don't have a PW, you will get an error trying to
create it (more on that later). It will still be created, but will
never run.

Right click the new Command Prompts task and choose Run and a command
window should open immediately. If not, something is wrong. If yes,
your mechanism is sound. Look in the log file to see your results.

You know how to remove the log now, so that is up to you. Be sure
the
Task Scheduler service is running again.

Try to Run your troublesome task, observe the columns, and the log.

If your task fails to run manually, the errors in the log file are
the
clues to what to do next.

The AV is Avira and I'm settting the task to run from within Avira. I
did the same thing on my Vista machine and it works fine. Same
settings on Power also (they're both laptops plugged in.
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top