Re: Scheduler Dead.
From: Kenny M (nobody_at_nospam.nowhere)
Date: 04/28/04
- Next message: Yannis: "Error code seen on blue screen XP"
- Previous message: Jupiter Jones [MVP]: "Re: Need KB823291 Hotfix - how to get it without risking huge $$$$?"
- In reply to: anonymous_at_discussions.microsoft.com: "Re: Scheduler Dead."
- Next in thread: Kenny M: "Re: Scheduler Dead."
- Reply: Kenny M: "Re: Scheduler Dead."
- Messages sorted by: [ date ] [ thread ]
Date: Thu, 29 Apr 2004 01:37:20 +1000
Jack,
Let me tell you what I'm thinking, but I haven't finished testing yet.
a) If you look at the NetDetect task Schedule tab, there's a down arrow on
the right so you can see the other schedules in "multiple schedules". The
2nd NetDetect schedule on mine is "at user logon".
b) Testing shows that Task Scheduler won't start a repetitive task if the
previous repetition is still running.
c) If a task is scheduled to run at user logon and every 5 minutes (from an
independent start time, not user logon), then there's a statistical chance
the 2nd task will try to start while the 1st is still running.
d) Hypothesis: If this happens, NetDetect (not Task Manager) seems to go
into a coma.
e) If that is the case, the solution would seem to be to delete the "at user
logon" part of the "multiple schedule". For dial-up there's never going to
be a connection available at user logon, so it seems a bit pointless. Don't
know about DSL.
I don't understand routers, so I don't know what additional complication
that would add.
Can't help with the IdleTask log entry either - the only entries in my log
are the Task Scheduler start/stop and my actual scheduled tasks start/stop.
HTH, Kenny.
"anonymous@discussions.microsoft.com" <email@suppressed> scribed thusly in
message
news:584e01c42d2d$4aaf09a0$a101280a@phx.gbl
> I'll tack a response about the log onto your message below.
> In response to your questions:
>
> 1. I reboot very rarely. Not often enough to notice
> correlation between Scheduler's functionality and
> rebooting.
>
> 2. I have DSL service but I've got a router set up serving
> my house, so my PC just sees a LAN. It gets an IP via
> DHCP.
>
> 3. Yes. Symantec NetDetect has "Multiple schedule
> times". Properties -> Schedule shows it running "Every 5
> minute(s) from 12:49 PM for 24 hour(s) every day,
> starting" on the day I installed it.
>
> 4. I'll keep an eye on NetDetect's behavior after reboot.
> My log file is filled with hundreds of entries like this
> that make the file nearly non-human-readable:
> "IdleTask" (TaskId1)
> Started 4/28/2004 1:40:37 AM
> I don't know what that is. Why is "IdleTask" a scheduled
> event? Sounds like a good name for a virus-type process;
> it's innocuous and obscure.
>
> 5. I only found services.msc earlier today, thanks to this
> forum. I decided against restarting the Task Scheduler
> before hearing what the forum had to say about it, so I
> could test suggestions in my system's "natural"
> environment.
>
> Hope this has been helpful.
> -Jack
>
>> -----Original Message-----
>> Jack,
>>
>> I've been chasing the same problem, which I would describe as
>> "Scheduler Coma" rather than "Scheduler Dead". My Task Scheduler
>> service is set to Automatic and is Started, but some days (I power
>> off overnight) scheduled tasks run, other days not. And you mention
>> Norton's Live Update. Could you answer a few questions for me?
>>
>> 1) How often do you reboot? (If you're using the PC as an alarm
>> clock, probably not daily).
>>
>> 2) Are you on dial-up or cable/DSL?
>>
>> 3) Does your Symantec NetDetect task say "Multiple Schedules"?
>>
>> 4) Have you ever looked at the Task Scheduler log 15+ minutes after
>> a reboot and NOT having started your ISP connection and observed
>> only 2 runs of NetDetect (and NO 3rd or subsequent runs) and the 2
>> runs are NOT 5 minutes apart?
>>
>> 5) Does stopping and starting the Task Scheduler service fix the
>> problem? It does on my PC - until I reboot next morning.
>>
>> "Jack" <email@suppressed> scribed thusly in message
>> news:543001c42d0d$c0798270$a401280a@phx.gbl
>>
>>> After 4 months running XP Pro with almost no problems,
>>> Scheduled Tasks simply stopped running.
>>>
>>> This includes the WinAmp playlists I'd scheduled to run as
>>> an alarm clock and Norton Antivirus's virus scans and Live
>>> Updates. All of this had been working since January.
>>>
>>> I scheduled some tasks for 1 minute in the future to see
>>> exactly what Scheduler had to say at the appointed time.
>>> Here's what happens when a scheduled task fails: Nothing!
>>> Nothing at all! The "status" column remains BLANK. Until
>>> somewhere between 8 and 12 hours later when XP pops up
>>> a "Some tasks that were scheduled to run may have been
>>> missed" dialog.
>>>
>>> This is NOT a password problem. If I right click on a
>>> task and select "run," it runs. In fact, if I run a task
>>> that way, then schedule it to run 1 minute in the future,
>>> it WILL run. But if I follow the same procedure and
>>> schedule the task to run, say, 8hrs in the future, the
>>> task fails. The time comes and goes and Scheduler doesn't
>>> even notice.
>>>
>>> I'm at a loss. I have no idea what the problem is or how
>>> to go about fixing it. Suggestions?
>>>
>>> -Jack
>>> (cross-posted to Security & Administration)
>>
>> .
- Next message: Yannis: "Error code seen on blue screen XP"
- Previous message: Jupiter Jones [MVP]: "Re: Need KB823291 Hotfix - how to get it without risking huge $$$$?"
- In reply to: anonymous_at_discussions.microsoft.com: "Re: Scheduler Dead."
- Next in thread: Kenny M: "Re: Scheduler Dead."
- Reply: Kenny M: "Re: Scheduler Dead."
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
