Task Scheduler unreliable in NT/2000/XP

From: Mike Reed (mike.google_at_compusolve-us.com)
Date: 02/17/04 

Date: 16 Feb 2004 16:49:25 -0800

I have encountered a problem with Windows Task Scheduler at many
client sites over the years, where tasks may run flawlessly for days
or weeks, then magically - they stop running (listing "Could Not
Start" for the task's status). To correct the problem, I simply have
to re-enter the task's password - the SAME password that has always
been there. The task will then run for several more days/weeks! This
has been a problem in Windows NT 4.0(sp6a) SERVERs AND XP Prof
workstations. And no surprise, since XP probably uses some of the
same underlying code as NT! I have talked with other consultants -
and we've all concluded that Microsoft's task scheduler is "unreliable
at best". I would love to find out the real cause of the problem and
solve this once and for all... More info: generally a single domain
exists, YES user account associated with task ALWAYS has/had a
password...

SchedLog.txt reports: The attempt to retrieve account information for
the specified task failed; therefore, the task did not run. Either an
error occurred, or no account information existed for the task. The
specific error is: 0x8004130f: No account information could be found
in the Task Scheduler security database for the task indicated.

How does Windows lose the "account information"? I can log in as the
same user assigned to the task - without a problem!

Thanks to all,

-Mike

Relevant Pages

  • Task Scheduler: tasks fail to run after several days or weeks. Have to reenter tasks password!
    ... Windows NT 4.0SERVERs AND XP Prof workstations. ... that Microsoft's task scheduler is "unreliable at best". ... or no account information existed for the task. ... found in the Task Scheduler security database for the task indicated. ...
    (microsoft.public.windowsxp.security_admin)
  • Re: Windows XP - Task Scheduler
    ... Windows NT 4.0SERVERs AND XP Prof workstations. ... that Microsoft's task scheduler is "unreliable at best". ... The attempt to retrieve account information ... found in the Task Scheduler security database for the task indicated. ...
    (microsoft.public.windowsxp.security_admin)
  • Re: Task Scheduler unreliable in NT/2000/XP
    ... A couple of causes of this problem were corrected in one of the Windows 2000 ... I have talked with other consultants -> and we've all concluded that Microsoft's task scheduler is "unreliable ... generally a single domain> exists, YES user account associated with task ALWAYS has/had a ... or no account information existed for the task. ...
    (microsoft.public.windowsxp.security_admin)
  • Re: Task Scheduler unreliable in NT/2000/XP
    ... There is a known issue with the Task Scheduler: It loses all account ... YES user account associated with task ALWAYS has/had a ... or no account information existed for the task. ...
    (microsoft.public.windowsxp.security_admin)
  • Re: User ID missing?
    ... There is no problem in having user account objects that have only the "user ... > When I look at the account information for some of my ... > My question is what is the impact of not having a Windows ...
    (microsoft.public.win2000.active_directory)