Establishing a Scheduled Task

F

FLKULCHAR

I am trying to schedule Disk Cleanup to run on a schedule -- I always get the
following error message:

"The new task has been created, but may not run because the account
information could not be set.
The specific error is:
Ox80041310:Unable to establish existence of the account specified."

Please help,
FLKulchar
 
A

Andrew McLaren

FLKULCHAR said:
I am trying to schedule Disk Cleanup to run on a schedule -- I always get the
following error message:

"The new task has been created, but may not run because the account
information could not be set.
The specific error is:
Ox80041310:Unable to establish existence of the account specified."

This is a common error message to get from the Task Scheduler, and it is
usually genuine (not misleading) - the task has been configured to run
with credentials which the scheduler service cannot recognise. Either
the account nme is invalid (eg account name has been changed), or the
account's password has expired.

What user context have you configured to use, when this task runs? The
user name and password for the user context (ie, the account the task
runs under) must be correct.

A Best Practice is to create a separate, dedicated user account to run
scheduled tasks. Don't use your own interactive login user account. Set
this task account so the password never expires (and optionally, deny
network access etc, for better security). Then configure your task to
run in the context of this dedicated account.


Hope it helps,

Andrew
 
J

Jose

I am trying to schedule Disk Cleanup to run on a schedule -- I always getthe
following error message:

"The new task has been created, but may not run because the account
information could not be set.
The specific error is:
     Ox80041310:Unable to establish existence of the account specified."

Please help,
FLKulchar

The account you use to run the task MUST have a password, so add a PW
to your account or create a new user with a password just for the
tasks. I think I will get an argument on that, so it depends on of
you want to fix it right now or screw around with it and fix it later.

There is a scheduled task log file in c:\windows called schedlgu.txt.
To get a fresh start with the log file, stop the Task Scheduler
service, delete the log file, restart the Task Scheduler service. The
log file is sometimes hard to read, so starting it over is sometimes
good for troubleshooting. After clearing it out and restarting the
service, you should see a message in the log file.

Your scheduled tasks are in the C:\windows\tasks folder. You should
see any you created there, or you can just navigate there and crate a
new task. This is easier for me than messing around with all the
Start, Programs... stuff. A task is just a file in a folder.

Create a simple task - like to run cmd.exe using the account that now
has a password. You should get no errors creating the task if you
have a valid account with a password. This is a really simple task
just for your testing. If you have no password, the task will get
created, but will never run.

Right click the task to Run it now. You should see a command prompt
window open immediately. If it does not work, look in the log file
for clues (probably no password). Try to get the simple CMD task to
run, then apply your knowledge to your other task. You can Google any
error messages, but a simple CMD task should be easy. If that doesn't
work, your other task won't work either.

When you create your new task, navigate to the tasks folder, right
click, Run it now and see if it works.

Troubleshoot as needed.
 

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

Similar Threads

Scheduling cleanup & defrag 1
Task Scheduler does not recognise account 1
Scheduled Task Fails. 6
Task Scheduler 1
Scheduled Task 6
Can't schedule tasks 3
Scheduled Tasks 10
scheduled tasks not starting 2

Top