Error - DCOM

[nh]

Archived from groups: microsoft.public.windowsxp.help_and_support (More info?)

Just the last couple of days my machine has developed a problem. Several
things start it, one being selecting print in Outlook Express. The print
window will eventually appear after 2 - 3 minutes and then everything works
OK. Another is trying to load up System Restore, again it takes several
minutes. (Incidently this started after a restore) When I look in the
event log the following appears each time

The server {0C0A3666-30C9-11D0-8F20-00805F2CD064} did not register with DCOM
within the required timeout.

Any suggestions as to what this is and how to sort it?

Neville

 

[Guest]

Archived from groups: microsoft.public.windowsxp.help_and_support (More info?)

{0C0A3666-30C9-11D0-8F20-00805F2CD064} is one of a long list of DCOM servers listed in Hkey_Classes_Root/CSLID/... I think you
probably upgraded some file on your system that is now looking for a version of the DCOM that is not now registered in your
(restored) registry. If you look it up, and find the file pointed to in the key
..../InProcServer32/default(=filename), then go to start run, and type REGSVR32 filename. This may register the proper file version.

If you find no entry, I don't know how you might find what you upgraded, but I'm guessing you will find it, and this procedure will
do nothing more than simply remake an existing DCOM entry, if no help.

--

Mark L. Ferguson
FAQ for MS Antispyware version 1.0.509
http://www.geocities.com/marfer_mvp/FAQ_MSantispy.htm
marfers notes for windows xp http://www.geocities.com/marfer_mvp/chatNotes.htm
..
"NH" <nh@NOSPAMm183.freeserve.co.uk> wrote in message news:d7kkep$35t$1@newsg2.svr.pol.co.uk...
> Just the last couple of days my machine has developed a problem. Several
> things start it, one being selecting print in Outlook Express. The print
> window will eventually appear after 2 - 3 minutes and then everything works
> OK. Another is trying to load up System Restore, again it takes several
> minutes. (Incidently this started after a restore) When I look in the
> event log the following appears each time
>
> The server {0C0A3666-30C9-11D0-8F20-00805F2CD064} did not register with DCOM
> within the required timeout.
>
> Any suggestions as to what this is and how to sort it?
>
> Neville
>
>
>

 

[nh]

Archived from groups: microsoft.public.windowsxp.help_and_support (More info?)

I tracked it down to the "machine debug manager". I disabled it and
everything is working fine. I just hope that I haven't created another
problem somewhere down the line.





"Mark L. Ferguson" <marfer_mvpREMOVE@hotmail.com> wrote in message
news:Op3rgG3ZFHA.3492@TK2MSFTNGP14.phx.gbl...
> {0C0A3666-30C9-11D0-8F20-00805F2CD064} is one of a long list of DCOM
> servers listed in Hkey_Classes_Root/CSLID/... I think you probably
> upgraded some file on your system that is now looking for a version of the
> DCOM that is not now registered in your (restored) registry. If you look
> it up, and find the file pointed to in the key
> .../InProcServer32/default(=filename), then go to start run, and type
> REGSVR32 filename. This may register the proper file version.
>
> If you find no entry, I don't know how you might find what you upgraded,
> but I'm guessing you will find it, and this procedure will do nothing more
> than simply remake an existing DCOM entry, if no help.
>
> --
>
> Mark L. Ferguson
> FAQ for MS Antispyware version 1.0.509
> http://www.geocities.com/marfer_mvp/FAQ_MSantispy.htm
> marfers notes for windows xp
> http://www.geocities.com/marfer_mvp/chatNotes.htm
> .
> "NH" <nh@NOSPAMm183.freeserve.co.uk> wrote in message
> news:d7kkep$35t$1@newsg2.svr.pol.co.uk...
>> Just the last couple of days my machine has developed a problem. Several
>> things start it, one being selecting print in Outlook Express. The print
>> window will eventually appear after 2 - 3 minutes and then everything
>> works
>> OK. Another is trying to load up System Restore, again it takes several
>> minutes. (Incidently this started after a restore) When I look in the
>> event log the following appears each time
>>
>> The server {0C0A3666-30C9-11D0-8F20-00805F2CD064} did not register with
>> DCOM
>> within the required timeout.
>>
>> Any suggestions as to what this is and how to sort it?
>>
>> Neville
>>
>>
>>
>
>