Re: Task Scheduler unreliable in NT/2000/XP

From: Pegasus \(MVP\) (I.can_at_fly.com)
Date: 02/17/04 

Date: Wed, 18 Feb 2004 06:57:37 +1100

Convert one of your machines to NTFS and see if it makes
a difference.

"Mike Reed" <mike.google@compusolve-us.com> wrote in message
news:59d35e76.0402170615.3b781644@posting.google.com...
> Thanks, but your explanation doesn't explain why Task Scheduler loses
> account information every few days up to several weeks. The changover
> from standard to DST (and back) only occurs twice a year...
>
>
> "Pegasus \(MVP\)" <I.can@fly.com> wrote in message
news:<#AaLPIP9DHA.1592@TK2MSFTNGP10.phx.gbl>...
> > There is a known issue with the Task Scheduler: It loses all account
> > details during the transition from standard time to daylight saving
> > time (and back), but only on machines where the system is installed
> > on a FAT32 partition. Machines with NTFS partitions are not
> > affected.
> >
> > Perhaps the same happens when you manually change the time
> > by more than a certain amount.
> >
> >
> > "Mike Reed" <mike.google@compusolve-us.com> wrote in message
> > news:59d35e76.0402161649.4a7d463a@posting.google.com...
> > > 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