"David Wang" <w3.4you@gmail.com> wrote in message
news:1171914024.127903.211040@a75g2000cwd.googlegroups.com...
> What happens if you go into SafeMode to run dcomcnfg to re-enable
> DCOM.
>
> I suspect it is some auto-start NT Service that requires DCOM and is
> now "hanging" and preventing you from fixing the situation. If so, you
> want to run in safe-mode to not have those extraneous services start,
> so that you can re-enable DCOM without their hinderance.
>
> Yes, Windows Server 2003 defaults with DCOM enabled, but it can be
> installed with DCOM disabled, and it is also user-configurable.
>
>> It really appears to involve the core
>> desktop functionality, as the desktop
>> takes a very long time to draw on startup
>
> What you can observe is very different from what is going on. I tend
> to agree with Roger about your hypothesis.
>
>
> //David
>
http://w3-4u.blogspot.com >
http://blogs.msdn.com/David.Wang > //
>
>
>
>
> On Feb 17, 6:24 pm, "Will" <westes-...@noemail.nospam> wrote:
>> "David Wang" <w3.4...@gmail.com> wrote in message
>>
>> news:1171706125.392056.84070@t69g2000cwt.googlegroups.com...
>>
>> > Can you go into Safe Mode to do what you need?
>>
>> I guess my question was what do I need to do to reinitialize DCOM. It's
>> not clear that safe mode helps here since it's not about stopping some
>> rogue
>> service (for example). I already enabled the registry option (per my
>> original post) that is required to "enable" DCOM, and yet DCOMCNFG
>> doesn't
>> show DCOM enabled after a reboot.
>>
>> > IIS6 on Windows Server 2003 does not use DCOM. Only if you switch it
>> > into IIS5 Compatibility Mode since by definition that must use DCOM
>> > for compatibility.
>>
>> Okay, I sense an educational moment coming on. :) First it appears our
>> developers had inadvertently installed IIS 5 when they installed an older
>> Visual Interdev. At least when I start IIS admin on the affected
>> machine
>> it shows version 5.0. So it looks like this is involved somehow with
>> this problem, although even then I am unclear on why turning off DCOM
>> broke
>> the entire computer, not just IIS 5.0.
>>
>> > Also, Windows Server 2003 runs without DCOM enabled.
>>
>> Just to be more elaborated on this point, every Windows 2003 standard and
>> web edition server I have installed leaves DCOM on. I trust your point
>> is
>> that it is safe to turn it off, and that makes sense, which is why the
>> result I got is all the more puzzling.
>>
>> > However, you may be running other 3rd party software on the server
>> > with NT Services that require DCOM. These services would be running on
>> > reboot, before and during your user login, so they may be breaking/
>> > hanging and causing your issues.
>>
>> It really appears to involve the core desktop functionality, as the
>> desktop
>> takes a very long time to draw on startup (maybe 10 minutes), and some
>> applications take a while to startup. Perhaps Interdev overwrote some
>> key
>> functionality for the desktop?
>>
>> --
>> Will
>
