ISWSIMBX
asked on
error 'Could Not Start' for Server 2003 Scheduled Task
Hello,
Has anyone experienced and solved a Server 2003 Scheduled Task error 'Could Not Start' where the task runs after setting the password, manually clicking 'Run', and then scheduling to run automatically within the next hour or so before the day changes? The scheduled task is defined on a Server 2003 SP2 domain controller.
When I then set the scheduled time to be 1 day in advance, the task does not run and we get a 'Could Not Start' error. After seeing the error, I set the password for the account the task runs under, then I can either manually run the task or schedule it to start within the next few hours and it runs fine. I do this daily and the task will keep running under these circumstances. I have moved the scheduled task to a different domain controller in our forest and the same circumstances happen.
Anyone see this error and it so have a solution?
Has anyone experienced and solved a Server 2003 Scheduled Task error 'Could Not Start' where the task runs after setting the password, manually clicking 'Run', and then scheduling to run automatically within the next hour or so before the day changes? The scheduled task is defined on a Server 2003 SP2 domain controller.
When I then set the scheduled time to be 1 day in advance, the task does not run and we get a 'Could Not Start' error. After seeing the error, I set the password for the account the task runs under, then I can either manually run the task or schedule it to start within the next few hours and it runs fine. I do this daily and the task will keep running under these circumstances. I have moved the scheduled task to a different domain controller in our forest and the same circumstances happen.
Anyone see this error and it so have a solution?
Sinder255248
What's the task running?
ASKER
The task is running a CMD file with Joe Richard's Oldcmp to disable AD user and server accounts.
You don't have a group policy which is applying the "Logon as a batch job" do you?
Computer configuration -> Windows settings > Security settings > Local policies > User rights assignments > Logon as a batch job
I'm wondering if group policy is overriding it.. when you enter the username and password again it's allowing it to logon, then as the policy applies it wipes it out.
Computer configuration -> Windows settings > Security settings > Local policies > User rights assignments > Logon as a batch job
I'm wondering if group policy is overriding it.. when you enter the username and password again it's allowing it to logon, then as the policy applies it wipes it out.
ASKER
As a matter of fact, our internal Domain Controller's Policy actually applies the 'Log on as a batch job' policy which I determined via RsoP on the Domain Controller where the scheduled tasks are defined and run.
Explain in detail please how this would cause the issue Im seeing.
Explain in detail please how this would cause the issue Im seeing.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
I added the domain account in the 'Logon as Batch Job', so give me a day or so to see the effects of this.
ASKER
That worked! The scheduled task is running daily without error. I very much appreciate the help here!
ASKER
Thanks for seeing this through,