Discussion Locked

Scheduled tasks not running

0 helpful
10 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

On a Windows 2000 server, I have scheduled a few back up batch files to run at night time. Everything has been working for a few years, but now has stopped. I figured out its because I have changed the Admin password on the server, I know change it often for security reasons, however since I have done this, the sheduled tasks do not run. When I checked, the run as box is filled in with admin.

Now, I am not sure if this is the cause, but its the only change I made to the server lately. Any ideas on how to get the schedules tasks to run again?

10 replies

by curlergirl

Since you changed the Administrator password, you have to reset the password for your scheduled tasks to match the new Administrator password. If you open the properties of the task, you should see an option to set the password for the task.

Hope this helps!

by maxwell edison

I agree with synergy/dlo.

I might add, however, when you try to assimilate new passwords into older tasks, you'll have a collective problem. These cybernetic-type attempts don't communicate with the hive very effectively, although they might be able to adapt, thus becoming even stronger programs. Or, if you wanted to attempt another regeneration cycle, you could try to write a drone program for the task, but these new implants might resist. And, as we know, resistance is futile.

by rindi1

Try to get services as these to run under the local System account and not under a user account who has a normal logon. Otherwise you'll always need to change those passwords as well whenever you change tha password for that user.

by aacinc

Yes, you are correct. You need to reset the password on each scheduled task to get them running again. You may want to setup an account that only has set permissions that you can use for the scheduled tasks.
At times I have noticed that the tasks do not run but have not figured out the cause. Resetting the password resolves the issue.

This discussion is closed to new replies.