Log on as batch job.... task scheduler not working....

  • Thread starter Thread starter Mike Holley
  • Start date Start date
M

Mike Holley

I one of our Windows 2000 domain controllers executing a batch file via the
task scheduler tool on a 15 minute interval. The batch job stops working
after a period of time and when I look through the task scheduler job log it
diplays the following:

"users.job" (users.bat) 9/29/2003 7:45:00 AM ** 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.

If I go back in and set the user account password on the job, it starts
working for a period of time and then quits working again.

I took a look through the domain controller and domain security policies and
noticed that the 'log on as batch job' has an account specified that the SID
does not resolve to an account. There are 4-5 other accounts that resolve no
problem. Is there any problems with removing the SID that does not resolve
to an account? I would assume that this means the account has been removed
and this reference is simply hanging around? Am I right in my thinking?

Thanks in advance,

Mike.
 
I one of our Windows 2000 domain controllers executing a batch file via the
task scheduler tool on a 15 minute interval. The batch job stops working
after a period of time and when I look through the task scheduler job log it
diplays the following:

"users.job" (users.bat) 9/29/2003 7:45:00 AM ** 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.

If I go back in and set the user account password on the job, it starts
working for a period of time and then quits working again.

I took a look through the domain controller and domain security policies and
noticed that the 'log on as batch job' has an account specified that the SID
does not resolve to an account. There are 4-5 other accounts that resolve no
problem. Is there any problems with removing the SID that does not resolve
to an account? I would assume that this means the account has been removed
and this reference is simply hanging around? Am I right in my thinking?

Thanks in advance,

Mike.
Click to expand...

You care right in your thinking.


Jerold Schulman
Windows: General MVP
JSI, Inc.
http://www.jsiinc.com
 
Back
Top