Solved

error 'Could Not Start' for Server 2003 Scheduled Task

Posted on 2008-06-24
9
2,125 Views
Last Modified: 2010-04-21
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
Comment
Question by:ISWSIMBX
  • 5
  • 4
9 Comments
 
LVL 8

Expert Comment

by:Sinder255248
ID: 21863309
What's the task running?  
0
 
LVL 3

Author Comment

by:ISWSIMBX
ID: 21864298
The task is running a CMD file with Joe Richard's Oldcmp to disable AD user and server accounts.
0
 
LVL 8

Expert Comment

by:Sinder255248
ID: 21864887
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
Independent Software Vendors: We Want Your Opinion

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

 
LVL 3

Author Comment

by:ISWSIMBX
ID: 21874096
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
 
LVL 8

Accepted Solution

by:
Sinder255248 earned 500 total points
ID: 21893385
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
 
LVL 8

Assisted Solution

by:Sinder255248
Sinder255248 earned 500 total points
ID: 21893387
Could you add the user which you're running the Task under to that GPO and see what happens?
0
 
LVL 3

Author Comment

by:ISWSIMBX
ID: 21894815
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
 
LVL 3

Author Comment

by:ISWSIMBX
ID: 21906689
That worked!  The scheduled task is running daily without error.  I very much appreciate the help here!
0
 
LVL 3

Author Closing Comment

by:ISWSIMBX
ID: 31470420
Thanks for seeing this through,
0

Featured Post

MS Dynamics Made Instantly Simpler

Make Your Microsoft Dynamics Investment Count  & Drastically Decrease Training Time by Providing Intuitive Step-By-Step WalkThru Tutorials.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

This article outlines the process to identify and resolve account lockout in an Active Directory environment.
Always backup Domain, SYSVOL etc.using processes according to Microsoft Best Practices. This is meant as a disaster recovery process for small environments that did not implement backup processes and did not run a secondary domain controller that ne…
This tutorial will walk an individual through the steps necessary to join and promote the first Windows Server 2012 domain controller into an Active Directory environment running on Windows Server 2008. Determine the location of the FSMO roles by lo…
Microsoft Active Directory, the widely used IT infrastructure, is known for its high risk of credential theft. The best way to test your Active Directory’s vulnerabilities to pass-the-ticket, pass-the-hash, privilege escalation, and malware attacks …

726 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question