Go Premium for a chance to win a PS4. Enter to Win

x
?
Solved

error 'Could Not Start' for Server 2003 Scheduled Task

Posted on 2008-06-24
9
Medium Priority
?
2,510 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
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.

 
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 2000 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 2000 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

Free Tool: Port Scanner

Check which ports are open to the outside world. Helps make sure that your firewall rules are working as intended.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

Question has a verified solution.

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

Wouldn't it be nice if objects in Active Directory automatically moved into the correct Organizational Units? This is what AutoAD aims to do and as a plus, it automatically creates Sites, Subnets, and Organizational Units.
Transferring FSMO roles is done when an admin wants to split roles between certain Domain Controllers or the Domain Controller holding the Roles has been forcefully demoted using dcpromo / forceremoval
This tutorial will walk an individual through the process of transferring the five major, necessary Active Directory Roles, commonly referred to as the FSMO roles to another domain controller. Log onto the new domain controller with a user account t…
This tutorial will walk an individual through the process of configuring their Windows Server 2012 domain controller to synchronize its time with a trusted, external resource. Use Google, Bing, or other preferred search engine to locate trusted NTP …

916 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