task scheduler error code 0x8004130f

  • Thread starter Thread starter debbie
  • Start date Start date
D

debbie

when trying to schedule tasks I get the error code 0x8004130f. Need an
idiot-proof way to correct. Help..
 
debbie said:
when trying to schedule tasks I get the error code 0x8004130f. Need an
idiot-proof way to correct. Help..
Click to expand...

- Make sure to use an account for the scheduled task that has a password.
- If you still have a problem, type the following into a Google search box:
task scheduler "0x8004130f"
You will get more than 500 hits.
 
when trying to schedule tasks I get the error code 0x8004130f. Need an
idiot-proof way to correct. Help..
Click to expand...

My standard copy/paste:


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 convenient time
require user intervention (answering questions). Does your
application have options to run unattended?

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 the
credentials part later.

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.
 
Back
Top