Re: Task Scheduler flaky in Win2003

Tech-Archive recommends: Fix windows errors by optimizing your registry

From: Jon Brammeier (anonymous_at_discussions.microsoft.com)
Date: 09/27/04 

Date: Mon, 27 Sep 2004 09:47:44 -0700

Well, let's see. The server is plugged into the wall. The
power is on. Fifty users access each of these servers 14
hours a day. Other applications on the servers seem to
work pretty well. These applications work flawlessly 14
hours a day . except when running from the Task
Scheduler, but only occasionally "freezing". VB6 apps
running through TS have worked flawlessly in this
environment for the past 3 years. This only seems to
occur with .NET 2003 executables running on Windows 2003
servers going through TS. Are you saying that a .NET app
is not reporting to the OS when its process ID has gone
out of scope?

>-----Original Message-----
>
>"Jon Brammeier" <jon.brammeier@fctg.com> wrote in message
>news:0c4801c4a26b$52827be0$a501280a@phx.gbl...
>> We run several executables through the task scheduler
on
>> our production servers on a regular basis. Most of them
>> are set to go off every 5 minutes throughout the day.
>> Recently, after moving some of the servers to Server
>> 2003, we have noticed that occasionally the task will
>> appear to hang. The scheduler shows it is still
running,
>> but task manager shows that it is not. You can't End
Task
>> because it isn't running. You have to restart the Task
>> Scheduler service. It seems random, but it's VERY
>> annoying.
>
>Before stating that the Task Scheduler is flaky, you
>should run some basic diagnostics, e.g. like so:
>
>@echo off
>echo %date% %time% Start of task >> c:\test.log
>echo User=%UserName%, Path=%path% >> c:\test.log
>c:\Tools\YourTask.exe 1>>c:\test.log 2>>c:\test.err
>echo %date% %time% End of task >> c:\test.log
>echo ====================>> c:\test.log
>
>After examining the two log files you might find that
>the flakiness is somewhere else . . .
>
>
>.
>

Relevant Pages

  • Re: Scheduled tasks copied between servers often do not run
    ... the Task Scheduler relies totally on %SystemRoot%\tasks. ... AFAIK no registry entries are involved. ... We are implementing dynamic Job monitoring across all the servers using ... echo %date% %time% Start of task> c:\test.log ...
    (microsoft.public.windowsxp.general)
  • Re: Using NT AuthoritySystem user in scheduled tasks affected on ONE server (out of many)..
    ... > Patched our Windows 2003 servers and rebooted them last night. ... > credentials) had their last state as "Could not Run". ... > unable to change task account information. ... Or is this a Task Scheduler thing? ...
    (microsoft.public.windows.server.general)
  • Re: Task scheduler: nothing happens
    ... > I got a similar problem on some of my servers. ... >>Thank you very much for your accurate help. ... > error message can be ... > Scheduler, because the Task ...
    (microsoft.public.win2000.general)
  • Re: Shutdown schedule and MS04-011
    ... If I run the shutdown from the command prompt it works, ... scheduler start the job then the server isn't lock it work too. ... I work for a very big firm and I have this problem on all servers. ...
    (microsoft.public.windows.server.setup)
  • Re: Task scheduler: nothing happens
    ... I got a similar problem on some of my servers. ... >I scheduled the batch file you proposed and... ... >> indicatior in the task scheduler window changes ... >> The calculator is not suitable to test the Task ...
    (microsoft.public.win2000.general)