D
Debbie
We applied several security patches to our database server
(currently Win 2000 Advanced Server 5.00.2195 SP4) on Jun
24 and since then our scheduled tasks normally do not run
with the following error:
"Stop FwakeTEST.job" (stop_fwake.bat) 7/28/2003 10:30:00
PM ** 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 that the task's Run-as name and password
are valid and try again.
Usually, but not always, if we re-enter the password in
the "Run as:" part of the task's properties, the task will
run the first time but fail with the above error on
subsequent attempts to run. About a week after this
started happening we applied SP4. But it did not fix the
problem. No passwords or user names have been changed.
As far as I know, there were no changes on our domain
server during this time.
I found a reference to the specific error that said to
give the local administrator group rights to log on as a
batch job. In the local policy setting window the account
that had always run the tasks does have a check mark in
the Local Policy Setting box, but does not have one in the
Effective Policy Setting box. Would that have anything to
do with this issue?
Anyone have any ideas on how to fix this problem? We have
been working with our network administrators for over a
month and still have not found a resolution.
Thanks,
Debbie
(currently Win 2000 Advanced Server 5.00.2195 SP4) on Jun
24 and since then our scheduled tasks normally do not run
with the following error:
"Stop FwakeTEST.job" (stop_fwake.bat) 7/28/2003 10:30:00
PM ** 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 that the task's Run-as name and password
are valid and try again.
Usually, but not always, if we re-enter the password in
the "Run as:" part of the task's properties, the task will
run the first time but fail with the above error on
subsequent attempts to run. About a week after this
started happening we applied SP4. But it did not fix the
problem. No passwords or user names have been changed.
As far as I know, there were no changes on our domain
server during this time.
I found a reference to the specific error that said to
give the local administrator group rights to log on as a
batch job. In the local policy setting window the account
that had always run the tasks does have a check mark in
the Local Policy Setting box, but does not have one in the
Effective Policy Setting box. Would that have anything to
do with this issue?
Anyone have any ideas on how to fix this problem? We have
been working with our network administrators for over a
month and still have not found a resolution.
Thanks,
Debbie