DCOM Error; Event ID 10010

[Guest]

Recently, on our Windows 2000 servers we started getting many DCOM error
messages, Event ID 10010:

DCOM server {0002DF01-0000-0000-C000-000000000064} could not register within
the timeout period

As a consequence, our IE based application started malfuncioning.

Obviously IE can not register its DCOM component.

Any idea/help/solution ?

TIA

 

[John John]

Search the registry for the GUID string
{0002DF01-0000-0000-C000-000000000064} Who owns it?

John

 

[Guest]

Local Administrators Group is the owner.

Search the registry for the GUID string
{0002DF01-0000-0000-C000-000000000064} Who owns it?

John

 

[John John]

I meant what program owns the GUID. Doesn't it say in the registry at
the {0002DF01-0000-0000-C000-000000000064} key? Usually to troubleshoot
these DCOM errors you first have to find what program makes the call
then take it from there. I looked for the key on 3 of my machines and
searched the net but I can't find any info on it. It's in your registry
somewhere, the DCOM server/component is called from the registry.

John

 

[Guest]

It's Internet Explorer.

TIA

I meant what program owns the GUID. Doesn't it say in the registry at
the {0002DF01-0000-0000-C000-000000000064} key? Usually to troubleshoot
these DCOM errors you first have to find what program makes the call
then take it from there. I looked for the key on 3 of my machines and
searched the net but I can't find any info on it. It's in your registry
somewhere, the DCOM server/component is called from the registry.

John

 

[John John]

Sorry, can't find any information on the GUID and Internet Explorer. Is
it possible that there is a typo? You posted
"{0002DF01-0000-0000-C000-000000000064}" I found an almost identical
error concerning IE but the GUID is
{0002DF01-0000-0000-C000-000000000046} (note the last 2 digits.)

If you can read german the information is here:
http://winfakten.dyndns.biz/dok98.html

Basically the guy says that he started getting DCOM errors 10010 in
Internet Explorer after installing security updates and that his fix was
to register IE dlls:

regsvr32 urlmon.dll
regsvr32 actxprxy.dll
regsvr32 scrrun.dll
regsvr32 mshtml.dll
regsvr32 shdocvw.dll
regsvr32 browseui.dll
regsvr32 msjava.dll

or repair IE if that fails.

If you don't use or need DCOM you could try disabling it and see what
happens. Other than that I can't offer any real solution to the
problem, maybe you might get an answer in the Internet Explorer groups,
one of the IE MVPs might be familiar with the error.

John

 

[Guest]

You are absolutely right about the GUID.

The last two digits are 46 (instead of 64, as I specified - dislexic !)

I'll try the suggested solution and let you know.

Thanks a bunch John !