Re: Task Scheduler flaky in Win2003
From: jonb (jonb_at_discussions.microsoft.com)
Date: 01/07/05
- Next message: Phillip Renouf: "Re: Disk Mangement Advice"
- Previous message: John: "Re: Remote access"
- Messages sorted by: [ date ] [ thread ]
Date: Fri, 7 Jan 2005 08:35:03 -0800
Let's try again. We have 3 tasks running in task scheduler on W2003 servers.
The servers are configured (nearly) identically and they are the same 3 tasks
on all servers. One app is VB6 and the other two are .NET. After running fine
for a number of days, task scheduler will fail to recognize that the app has
closed. The status shows Running, but it's not. Task Scheduler will not
restart it, because it thinks it's still running. The only way to clear it is
to restart the service.
Once this pattern has begun, it will continue randomly until the server is
rebooted. Some of the servers have been up for 60-90 days without exhibiting
this problem. Others may start it after running for just a few weeks.
If you don't like the word "flaky", then ignore it. Just give me something
constructive to work with.
"Pegasus (MVP)" wrote:
> 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 . . .
> > >
> > >
> > >.
> > >
>
>
>
- Next message: Phillip Renouf: "Re: Disk Mangement Advice"
- Previous message: John: "Re: Remote access"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
