• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 2866
  • Last Modified:

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?
0
ISWSIMBX
Asked:
ISWSIMBX
  • 5
  • 4
2 Solutions
 
Sinder255248Commented:
What's the task running?  
0
 
ISWSIMBXAuthor Commented:
The task is running a CMD file with Joe Richard's Oldcmp to disable AD user and server accounts.
0
 
Sinder255248Commented:
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.
0
Making Bulk Changes to Active Directory

Watch this video to see how easy it is to make mass changes to Active Directory from an external text file without using complicated scripts.

 
ISWSIMBXAuthor 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.
0
 
Sinder255248Commented:
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.  
0
 
Sinder255248Commented:
Could you add the user which you're running the Task under to that GPO and see what happens?
0
 
ISWSIMBXAuthor 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.
0
 
ISWSIMBXAuthor Commented:
That worked!  The scheduled task is running daily without error.  I very much appreciate the help here!
0
 
ISWSIMBXAuthor Commented:
Thanks for seeing this through,
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Simplify Active Directory Administration

Administration of Active Directory does not have to be hard.  Too often what should be a simple task is made more difficult than it needs to be.The solution?  Hyena from SystemTools Software.  With ease-of-use as well as powerful importing and bulk updating capabilities.

  • 5
  • 4
Tackle projects and never again get stuck behind a technical roadblock.
Join Now