Appreciate the response. I double checked all 3 servers
and all are using NTFS system partitions and have been
since going into production. I'm not exactly clear what
is meant by playing w/ the system date/time. I do call
the XSET32 library to insert a date stamp in the file name
of the backup01.log file, however that is done through a
separate scheduled task and batch file which runs several
hours after the backup has run. Could you fill me a bit
more? Is this an issue I should open a TAC with Microsoft
for?
>
>
The problem you report is usually encountered on machines
that use a FAT32 file system for the system drive, on the
day when Daylight Saving Time changes (I know this sounds
improbable but that's the way it is). Are you perhaps
playing with the system date/time?


"Ben Hinshaw" <(E-Mail Removed)> wrote
in message
news:1e9301c3bdd6$61470080$(E-Mail Removed)...
> I am attempting to use Task Scheduler on 3 servers
running > 2K Server SP4. Each night at 11, the scheduler
calls on a > batch file to run the designated backups for
that night. I have assigned the Run as: account to the
local administrator and password account. Everything,
every night works fine for approx. a week to a week and a
half before I begin getting the following error:
> The attempt to log on to the account associated with the
> task failed, therefore, the task did not run. The
> specific error is: 0x80070569: Logon failure: the user
> has not been granted the requested logon type at this
> computer. Verify the task's Run-as name and password are
> valid and try again. I will then re-enter the admin
password and things work fine again for another week
before getting the same errors again. Technet article
328773, refers to this similar error which was supposed to
be fixed in SP4, however that's what I'm running and still
getting these errors.
>
> Any help is greatly appreciated!


..

What I meant was: If you change the system date or time of
a Win2000 installation that uses a FAT32 system partition
then your scheduled tasks are likely to fail.

Since your file system is NTFS, this does not apply. I'm
afraid I have no further suggestions.


"Ben Hinshaw" <(E-Mail Removed)> wrote in message
news:0a6f01c3be6f$d44d9f50$(E-Mail Removed)...
> Appreciate the response. I double checked all 3 servers
> and all are using NTFS system partitions and have been
> since going into production. I'm not exactly clear what
> is meant by playing w/ the system date/time. I do call
> the XSET32 library to insert a date stamp in the file name
> of the backup01.log file, however that is done through a
> separate scheduled task and batch file which runs several
> hours after the backup has run. Could you fill me a bit
> more? Is this an issue I should open a TAC with Microsoft
> for?
> >
> >
> The problem you report is usually encountered on machines
> that use a FAT32 file system for the system drive, on the
> day when Daylight Saving Time changes (I know this sounds
> improbable but that's the way it is). Are you perhaps
> playing with the system date/time?
>
>
> "Ben Hinshaw" <(E-Mail Removed)> wrote
> in message
> news:1e9301c3bdd6$61470080$(E-Mail Removed)...
> > I am attempting to use Task Scheduler on 3 servers
> running > 2K Server SP4. Each night at 11, the scheduler
> calls on a > batch file to run the designated backups for
> that night. I have assigned the Run as: account to the
> local administrator and password account. Everything,
> every night works fine for approx. a week to a week and a
> half before I begin getting the following error:
> > The attempt to log on to the account associated with the
> > task failed, therefore, the task did not run. The
> > specific error is: 0x80070569: Logon failure: the user
> > has not been granted the requested logon type at this
> > computer. Verify the task's Run-as name and password are
> > valid and try again. I will then re-enter the admin
> password and things work fine again for another week
> before getting the same errors again. Technet article
> 328773, refers to this similar error which was supposed to
> be fixed in SP4, however that's what I'm running and still
> getting these errors.
> >
> > Any help is greatly appreciated!
>
>
> .
>
>