error 'Could Not Start' for Server 2003 Scheduled Task

ISWSIMBX
ISWSIMBX used Ask the Experts™
on
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?
Comment
Watch Question

Do more with

Expert Office
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®
What's the task running?  

Author

Commented:
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.
Ensure you’re charging the right price for your IT

Do you wonder if your IT business is truly profitable or if you should raise your prices? Learn how to calculate your overhead burden using our free interactive tool and use it to determine the right price for your IT services. Start calculating Now!

Author

Commented:
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.
Sorry been away for a couple of days.  When you schedule a job it sticks your name into that allow list so that you can run the job as a batch user (instead of being logged on).  If you're clearing that list out with a group policy, you're clearing out the entry that was put in there by the Tast scheduler.  This means that the task can't run because this user doesn't have the permissions to logon without an interactive session.  
Could you add the user which you're running the Task under to that GPO and see what happens?

Author

Commented:
I added the domain account in the 'Logon as Batch Job', so give me a day or so to see the effects of this.

Author

Commented:
That worked!  The scheduled task is running daily without error.  I very much appreciate the help here!

Author

Commented:
Thanks for seeing this through,

Do more with

Expert Office
Submit tech questions to Ask the Experts™ at any time to receive solutions, advice, and new ideas from leading industry professionals.

Start 7-Day Free Trial