Re: Task Scheduler flaky in Win2003

From: Pegasus \(MVP\) (I.can_at_fly.com)
Date: 09/27/04


Date: Tue, 28 Sep 2004 07:52:38 +1000

I'm no saying anything other than this: Before claiming that a
certain piece of software is flaky, I like to get my facts right.
Quite often this requires a detailed collection of evidence.
Drawing conclusions too early in the process can greatly
prolong the duration of the trouble shooting exercise.

"Jon Brammeier" <anonymous@discussions.microsoft.com> wrote in message
news:46af01c4a4b1$b620dc30$a601280a@phx.gbl...
> 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: Proposal for a new PKI model (At least I hope its new)
    ... Are you saying that we should simply ... > shift the CA task to the root DNS Name servers themselves? ... that you could use a SSL domain name certificate for something else ...
    (sci.crypt)
  • Re: Transfering domain authority
    ... I'm not saying you can't host your own, I do that, but I have three DNS ... servers, two of which answer only to the public requests. ...
    (microsoft.public.win2000.dns)
  • Re: Yep, some more actual Mac advocacy (This is comp.sys.mac.advocacy, after all)
    ... But you aren't saying how they accomplished that, ... or why other manufacturers didn't manage it. ... Well, I was not able to physically access 90% of our servers so, yes, it was an advantage. ... Just another toner monkey, eh? ...
    (comp.sys.mac.advocacy)
  • Re: WDW Tipping / Dining
    ... I think we don't really disagree. ... What you're saying, in effect, is that the ... of* the tip is simply paying the servers' compensation. ... As for the confusion and frustration for *some* customers, ...
    (rec.arts.disney.parks)
  • Re: Task Scheduler flaky in Win2003
    ... We have 3 tasks running in task scheduler on W2003 servers. ... restart it, because it thinks it's still running. ... If you don't like the word "flaky", ...
    (microsoft.public.windows.server.general)