Task Scheduler Non Functional in Windows 2000 Server

  • Thread starter Thread starter robboll
  • Start date Start date
R

robboll

Windows 20000
Version 5.0 (Build 2195: Service Pack 4)

Logging on as an Administrator User I open Control Panel and Scheduled
Tasks and:

1. Click "Add Scheduled Task" and click "Next"
2. Select an Application (e.g., Command Prompt) and click "Next"
3. Click "Daily" and click "Next"
4. Set Start time for one minute in the future (for testing), click
"Next"
5. Enter and Confirm your password.
6. Wait for the Application to execute.

What happens with this server is:

The Status shows "Running" but there is no Application execution. The
application does not show up as running in the Task Manager.

Is this a known issue? Maybe a patch or something that kills the Task
Manager in Windows Server 2000?
Any responses greatly appreciated!

RBollinger
 
Scheduled Tasks|Advanced|View Log may provide some details.

--
Regards,

Dave Patrick ....Please no email replies - reply in newsgroup.
Microsoft Certified Professional
Microsoft MVP [Windows]
http://www.microsoft.com/protect

:
| Windows 20000
| Version 5.0 (Build 2195: Service Pack 4)
|
| Logging on as an Administrator User I open Control Panel and Scheduled
| Tasks and:
|
| 1. Click "Add Scheduled Task" and click "Next"
| 2. Select an Application (e.g., Command Prompt) and click "Next"
| 3. Click "Daily" and click "Next"
| 4. Set Start time for one minute in the future (for testing), click
| "Next"
| 5. Enter and Confirm your password.
| 6. Wait for the Application to execute.
|
| What happens with this server is:
|
| The Status shows "Running" but there is no Application execution. The
| application does not show up as running in the Task Manager.
|
| Is this a known issue? Maybe a patch or something that kills the Task
| Manager in Windows Server 2000?
| Any responses greatly appreciated!
|
| RBollinger
|
 
The log file schedlgu.txt doesn't provide much information:

****************************************************************
"notepad.job" (notepad.exe) 12/13/2004 9:02:34 AM ** WARNING **
The task was terminated. This action was initiated either by an
administrator or by the Task Scheduler service (because, for example,
the computer is now non idle).
"Command Prompt.job" (CMD.EXE)
Started 12/13/2004 9:16:00 AM
"Command Prompt.job" (CMD.EXE) 12/13/2004 9:22:26 AM ** WARNING **
The task was terminated. This action was initiated either by an
administrator or by the Task Scheduler service (because, for example,
the computer is now non idle).
"notepad.job" (notepad.exe)
Started 12/13/2004 2:52:08 PM
"notepad.job" (notepad.exe) 12/13/2004 3:47:13 PM ** WARNING **
The task was terminated. This action was initiated either by an
administrator or by the Task Scheduler service (because, for example,
the computer is now non idle).
[ ***** Most recent entry is above this line ***** ]
****************************************************************

The reason it says in each case that "The task was terminated" is
because it says "Running" when it isn't. It would stay there
indefinitely if I didn't terminate it.

I am thinking that a service update broke the Task Scheduler, but I
don't know which one. I thought this might be a known problem.
 
You would get this effect if you used a username and password for the job
different than the current logged on user..

--
Regards,

Dave Patrick ....Please no email replies - reply in newsgroup.
Microsoft Certified Professional
Microsoft MVP [Windows]
http://www.microsoft.com/protect

:
| The log file schedlgu.txt doesn't provide much information:
|
| ****************************************************************
| "notepad.job" (notepad.exe) 12/13/2004 9:02:34 AM ** WARNING **
| The task was terminated. This action was initiated either by an
| administrator or by the Task Scheduler service (because, for example,
| the computer is now non idle).
| "Command Prompt.job" (CMD.EXE)
| Started 12/13/2004 9:16:00 AM
| "Command Prompt.job" (CMD.EXE) 12/13/2004 9:22:26 AM ** WARNING **
| The task was terminated. This action was initiated either by an
| administrator or by the Task Scheduler service (because, for example,
| the computer is now non idle).
| "notepad.job" (notepad.exe)
| Started 12/13/2004 2:52:08 PM
| "notepad.job" (notepad.exe) 12/13/2004 3:47:13 PM ** WARNING **
| The task was terminated. This action was initiated either by an
| administrator or by the Task Scheduler service (because, for example,
| the computer is now non idle).
| [ ***** Most recent entry is above this line ***** ]
| ****************************************************************
|
| The reason it says in each case that "The task was terminated" is
| because it says "Running" when it isn't. It would stay there
| indefinitely if I didn't terminate it.
|
| I am thinking that a service update broke the Task Scheduler, but I
| don't know which one. I thought this might be a known problem.
 
robboll said:
The log file schedlgu.txt doesn't provide much information:
Click to expand...

Or does it? You don't, by chance, have the
<Terminate The Task if the Computer Ceases to be Idle> box checked on
the settings page?

Just a guess...


Dr. Know
 
I am logging in to the server as JoeUser who has Administrative
permissions. I set up the job as joe user and authenticate with
JoeUser's password. When the job kicks off, the Status turns to
Running, but Task Manager doesn't show the running application. the
logfile: Schedlgu.txt indicates the task started and will stay that way
until I kill the task.

I've tried running Scheduled Tasks on several of our servers and they
all result in the same. I am the Administrator of all of these servers
and haven't had a problem with the Task Scheduler until recently. I am
thinking that it could have been a Microsoft update that is causing the
problem, but haven't received any feedback from the newsgroups.
 
You might try something simple. Schedule to run C:\WINNT\system32\calc.exe
It might be possible your cmd.exe window is just off the limits of the
screen. Also try logging on as a different user.

--
Regards,

Dave Patrick ....Please no email replies - reply in newsgroup.
Microsoft Certified Professional
Microsoft MVP [Windows]
http://www.microsoft.com/protect

:
|I am logging in to the server as JoeUser who has Administrative
| permissions. I set up the job as joe user and authenticate with
| JoeUser's password. When the job kicks off, the Status turns to
| Running, but Task Manager doesn't show the running application. the
| logfile: Schedlgu.txt indicates the task started and will stay that way
| until I kill the task.
|
| I've tried running Scheduled Tasks on several of our servers and they
| all result in the same. I am the Administrator of all of these servers
| and haven't had a problem with the Task Scheduler until recently. I am
| thinking that it could have been a Microsoft update that is causing the
| problem, but haven't received any feedback from the newsgroups.
|
 
robboll said:
I am logging in to the server as JoeUser who has Administrative
permissions. I set up the job as joe user and authenticate with
JoeUser's password. When the job kicks off, the Status turns to
Running, but Task Manager doesn't show the running application. the
logfile: Schedlgu.txt indicates the task started and will stay that way
until I kill the task.
Click to expand...

We have no problems running tasks here - with Server 2000 SP4 and all
available updates on several machines.

According to the schedlgu.txt you posted:

****************************************************************
"Command Prompt.job" (CMD.EXE)
Started 12/13/2004 9:16:00 AM
"Command Prompt.job" (CMD.EXE) 12/13/2004 9:22:26 AM ** WARNING **
The task was terminated. This action was initiated either by an
administrator or by the Task Scheduler service (because, for example,
the computer is now non idle).
****************************************************************

Your log implies that the task was started and ran for 6 minutes:26
seconds, but was terminated due to administrative action or the task
scheduler killed the job due to activity at the computer - if the job
settings are enabled to terminate the job with computer activity.

The task job settings tab has an option check box to:
<Terminate The Task if the Computer Ceases to be Idle>

Any Mouse or keyboard activity at the computer will terminate the job.
Including checking the task manager for active processes...

Again, Have you checked this setting?
It works fine on all of our 2000 servers - I just tried it with
calc.exe on our 5 machines!

If you have terminal server or remote desktop running, you can check
the task manager remotely from another computer and this activity is
NOT logged as local activity - thereby NOT canceling the task.

Also, you must have the Task Scheduler dependency RPC enabled and
running for Task Scheduler to work.

??


Dr. Know
 
Back
Top