|
web
newsgroups
|
|||||||||||||||||||||||
|
|||||||||||||||||||||||
Task Scheduler won't workThe last weeks, the Task Scheduler in Win2000 Pro has begun to let me dowm.
More often than not, my scheduled tasks (among them various backups) will not be performed, and the scheduled task reports that it "could not be started". If I change the scheduled time, the task may start next time - but only once; after that it tells me again that it could not be started. Does anyone have a clue??? Scheduled Tasks|Advanced|View Log may provide some details. Also check Event
Viewer for errors. -- Show quoteHide quoteRegards, Dave Patrick ....Please no email replies - reply in newsgroup. Microsoft Certified Professional Microsoft MVP [Windows] http://www.microsoft.com/protect "Hans Näslund" wrote: | The last weeks, the Task Scheduler in Win2000 Pro has begun to let me dowm. | More often than not, my scheduled tasks (among them various backups) will | not be performed, and the scheduled task reports that it "could not be | started". | | If I change the scheduled time, the task may start next time - but only | once; after that it tells me again that it could not be started. | | Does anyone have a clue??? | | If all else fails (as it did for me), here's a workaround that may help: Set up
multiple schedules in each task...but be sure to allow enough time between starts for the event to run (just in case both do actually start). I found that the first scheduled time will get the "could not be started" error, but the next one will run. In my case I make daily backups of the registry using URUNT. The time between the first and second start times is only two minutes. Show quoteHide quote "Hans Näslund" <hans.nasl***@spray.se> wrote in message news:OCF%d.133039$dP1.471222@newsc.telia.net... > The last weeks, the Task Scheduler in Win2000 Pro has begun to let me dowm. > More often than not, my scheduled tasks (among them various backups) will > not be performed, and the scheduled task reports that it "could not be > started". > > If I change the scheduled time, the task may start next time - but only > once; after that it tells me again that it could not be started. > > Does anyone have a clue??? > > Typo...that should be ERUNT...sorry.
Show quoteHide quote "wayfarrer" <dontbot***@att.net> wrote in message news:uQ7rk5lLFHA.3868@TK2MSFTNGP10.phx.gbl... > If all else fails (as it did for me), here's a workaround that may help: Set up > multiple schedules in each task...but be sure to allow enough time between > starts for the event to run (just in case both do actually start). I found that > the first scheduled time will get the "could not be started" error, but the next > one will run. > > In my case I make daily backups of the registry using URUNT. The time between > the first and second start times is only two minutes. > > "Hans Näslund" <hans.nasl***@spray.se> wrote in message > news:OCF%d.133039$dP1.471222@newsc.telia.net... > > The last weeks, the Task Scheduler in Win2000 Pro has begun to let me dowm. > > More often than not, my scheduled tasks (among them various backups) will > > not be performed, and the scheduled task reports that it "could not be > > started". > > > > If I change the scheduled time, the task may start next time - but only > > once; after that it tells me again that it could not be started. > > > > Does anyone have a clue??? > > > > > > 
Other interesting topics
Time Issue
Direct Cable Connection - Is this included with W2K Pro ? Is it advisable to load three operating systems on diff drive on s Tape Backup Problem Loss of Thumbnails Print file without prompting for a printer chkdsk to the rescue -- But how worried should I be? Windows 2000 Server - freezes without a message Giving Task Scheduler Rights to Non-Admin User Script error |
|||||||||||||||||||||||
