WaitToKillServiceTimeout
http://www.microsoft.com/resources/d...ntry/26734.asp
Why not just disable both COM+ Event System & Task Scheduler?
I have them both disabled.
However, Task Scheduler service is needed if you use Prefetch.
This is the only downside that I see to having COM+ Event System service
disabled....
Note if disabling this service then at every boot there will be generated a
warning in the Event Log about this service not running.
--
Hope this helps. Let us know.
Wes
MS-MVP Windows Shell/User
In news:(E-Mail Removed),
Alec S. <@> hunted and pecked:
> Hi,
>
> This is the closest newsgroup I could find for what I need.
>
> I am looking for a way to specify the timeout for an NT service.
> Specifically, there are a couple of services that sometimes hang on
> startup (COM+ Event System, Task Scheduler) and this causes a massively
> long bootup (5+ minutes). Worse still, it seems to be doing this more
> and more often now. Since I have been unable to identify the cause
> (especially since it's intermittent), I have resigned myself to at least
> alleviate the symptom.
>
> I want to set the timeout to a smaller value so that if they do hang, I
> don't have to wait forever to get control of my system. Even if they were
> critical to the functioning of my system (they are not), I'd rather get
> control right away so that I can reboot and try again instead of waiting
> five minutes to try again.
>
> I've looked everywhere and while I can find the occasional mention of the
> existence of service timeout values, I can't find any mention on how to
> set them.
>
> Can anyone please tell me how I can do this? It's really driving me
> crazy.
>
>
> Thanks a lot.
>
> --
> Alec S.
> news/alec->synetech/cjb/net