Error DCOM 10010

S

Simon

HI,
I heve W2K sp4 with terminal services installed and all security updates
installed too, but and DCOM error still logged on system log many time.
This is the error:

Event Type: Error
Event Source: DCOM
Event Category: None
Event ID: 10010
Date: 3/20/2006
Time: 08:57:23 AM
User: Domain\administrator
Computer: ServerName
Description:
The server {E9376CC6-121A-447E-81CF-D8BCC200007C} did not register with DCOM
within the required timeout.

I have try to apply many KB from Microsoft support, but the error still
logged.
How to do I to solve this problem?

Thanks Simon.
 
J

John John

Search the registry for {E9376CC6-121A-447E-81CF-D8BCC200007C} and find
out which service owns it. You will then be able to narrow your
troubleshooting to that service.

John
 
S

Simon

On registry I have found this:

REGEDIT4

[HKEY_CLASSES_ROOT\CLSID\{E9376CC6-121A-447e-81CF-D8BCC200007C}]
"AppId"="{653C5148-4DCE-4905-9CFD-1B23662D3D9E}"
@="Updates Class"

[HKEY_CLASSES_ROOT\CLSID\{E9376CC6-121A-447e-81CF-D8BCC200007C}\InProcHandler32]
@="Ole32.dll"

[HKEY_CLASSES_ROOT\CLSID\{E9376CC6-121A-447e-81CF-D8BCC200007C}\LocalServer32]
@="C:\\WINNT\\system32\\svchost.exe"

P.S.
I have the error when I'am connected on server via Terminal Services
Administrator mode.
 
J

John John

I'm on an NT4 box so I can't check the values. Search again in the
registry for the application ID GUID

{653C5148-4DCE-4905-9CFD-1B23662D3D9E}

Just a guess but @="Updates Class" gives me a sneaking inkling that the
Windows Automatic Update service might be the culprit. You should find
out more when you get the results of the search on the AppId GUID.

If it does point to Windows Update service, for troubleshooting
purposes, try disabling or setting it to manual start and see if the
error stops. That will help confirm the source.

John
On registry I have found this:

REGEDIT4

[HKEY_CLASSES_ROOT\CLSID\{E9376CC6-121A-447e-81CF-D8BCC200007C}]
"AppId"="{653C5148-4DCE-4905-9CFD-1B23662D3D9E}"
@="Updates Class"

[HKEY_CLASSES_ROOT\CLSID\{E9376CC6-121A-447e-81CF-D8BCC200007C}\InProcHandler32]
@="Ole32.dll"

[HKEY_CLASSES_ROOT\CLSID\{E9376CC6-121A-447e-81CF-D8BCC200007C}\LocalServer32]
@="C:\\WINNT\\system32\\svchost.exe"

P.S.
I have the error when I'am connected on server via Terminal Services
Administrator mode.


Search the registry for {E9376CC6-121A-447E-81CF-D8BCC200007C} and find
out which service owns it. You will then be able to narrow your
troubleshooting to that service.

John
 
S

Simon

I have stop the Automatic Update service and the errors seem to be stopped.
Hhave you an idea to solve this problem ?

Thanks.

Simon


John John said:
I'm on an NT4 box so I can't check the values. Search again in the
registry for the application ID GUID

{653C5148-4DCE-4905-9CFD-1B23662D3D9E}

Just a guess but @="Updates Class" gives me a sneaking inkling that the
Windows Automatic Update service might be the culprit. You should find
out more when you get the results of the search on the AppId GUID.

If it does point to Windows Update service, for troubleshooting purposes,
try disabling or setting it to manual start and see if the error stops.
That will help confirm the source.

John
On registry I have found this:

REGEDIT4

[HKEY_CLASSES_ROOT\CLSID\{E9376CC6-121A-447e-81CF-D8BCC200007C}]
"AppId"="{653C5148-4DCE-4905-9CFD-1B23662D3D9E}"
@="Updates Class"

[HKEY_CLASSES_ROOT\CLSID\{E9376CC6-121A-447e-81CF-D8BCC200007C}\InProcHandler32]
@="Ole32.dll"

[HKEY_CLASSES_ROOT\CLSID\{E9376CC6-121A-447e-81CF-D8BCC200007C}\LocalServer32]
@="C:\\WINNT\\system32\\svchost.exe"

P.S.
I have the error when I'am connected on server via Terminal Services
Administrator mode.


Search the registry for {E9376CC6-121A-447E-81CF-D8BCC200007C} and find
out which service owns it. You will then be able to narrow your
troubleshooting to that service.

John

Simon wrote:

HI,
I heve W2K sp4 with terminal services installed and all security updates
installed too, but and DCOM error still logged on system log many time.
This is the error:

Event Type: Error
Event Source: DCOM
Event Category: None
Event ID: 10010
Date: 3/20/2006
Time: 08:57:23 AM
User: Domain\administrator
Computer: ServerName
Description:
The server {E9376CC6-121A-447E-81CF-D8BCC200007C} did not register with
DCOM within the required timeout.

I have try to apply many KB from Microsoft support, but the error still
logged.
How to do I to solve this problem?

Thanks Simon.
 
J

John John

Set Automatic Updates (wuauserv) to manual start? I don't know what the
fix for the error is. Not all applications or services are compatible
with Terminal Services, maybe there is a bug in wuauserv that we don't
know about. You might try asking on the Terminal Services or Windows
Updates groups, someone there might have an answer:

news://msnews.microsoft.com/microsoft.public.windows.terminal_services
news://msnews.microsoft.com/microsoft.public.windowsupdate

Or some else here might have a solution. You might need to start a new
thread wit a new subject line. Also, you might find something about the
problem by running dcomcnfg.exe, someone else will have to help you from
here on, I'm out of ideas.

John
I have stop the Automatic Update service and the errors seem to be stopped.
Hhave you an idea to solve this problem ?

Thanks.

Simon


I'm on an NT4 box so I can't check the values. Search again in the
registry for the application ID GUID

{653C5148-4DCE-4905-9CFD-1B23662D3D9E}

Just a guess but @="Updates Class" gives me a sneaking inkling that the
Windows Automatic Update service might be the culprit. You should find
out more when you get the results of the search on the AppId GUID.

If it does point to Windows Update service, for troubleshooting purposes,
try disabling or setting it to manual start and see if the error stops.
That will help confirm the source.

John
On registry I have found this:

REGEDIT4

[HKEY_CLASSES_ROOT\CLSID\{E9376CC6-121A-447e-81CF-D8BCC200007C}]
"AppId"="{653C5148-4DCE-4905-9CFD-1B23662D3D9E}"
@="Updates Class"

[HKEY_CLASSES_ROOT\CLSID\{E9376CC6-121A-447e-81CF-D8BCC200007C}\InProcHandler32]
@="Ole32.dll"

[HKEY_CLASSES_ROOT\CLSID\{E9376CC6-121A-447e-81CF-D8BCC200007C}\LocalServer32]
@="C:\\WINNT\\system32\\svchost.exe"

P.S.
I have the error when I'am connected on server via Terminal Services
Administrator mode.




Search the registry for {E9376CC6-121A-447E-81CF-D8BCC200007C} and find
out which service owns it. You will then be able to narrow your
troubleshooting to that service.

John

Simon wrote:


HI,
I heve W2K sp4 with terminal services installed and all security updates
installed too, but and DCOM error still logged on system log many time.
This is the error:

Event Type: Error
Event Source: DCOM
Event Category: None
Event ID: 10010
Date: 3/20/2006
Time: 08:57:23 AM
User: Domain\administrator
Computer: ServerName
Description:
The server {E9376CC6-121A-447E-81CF-D8BCC200007C} did not register with
DCOM within the required timeout.

I have try to apply many KB from Microsoft support, but the error still
logged.
How to do I to solve this problem?

Thanks Simon.
 
S

Simon

Thanks for all John.


John John said:
Set Automatic Updates (wuauserv) to manual start? I don't know what the
fix for the error is. Not all applications or services are compatible
with Terminal Services, maybe there is a bug in wuauserv that we don't
know about. You might try asking on the Terminal Services or Windows
Updates groups, someone there might have an answer:

news://msnews.microsoft.com/microsoft.public.windows.terminal_services
news://msnews.microsoft.com/microsoft.public.windowsupdate

Or some else here might have a solution. You might need to start a new
thread wit a new subject line. Also, you might find something about the
problem by running dcomcnfg.exe, someone else will have to help you from
here on, I'm out of ideas.

John
I have stop the Automatic Update service and the errors seem to be
stopped.
Hhave you an idea to solve this problem ?

Thanks.

Simon


I'm on an NT4 box so I can't check the values. Search again in the
registry for the application ID GUID

{653C5148-4DCE-4905-9CFD-1B23662D3D9E}

Just a guess but @="Updates Class" gives me a sneaking inkling that the
Windows Automatic Update service might be the culprit. You should find
out more when you get the results of the search on the AppId GUID.

If it does point to Windows Update service, for troubleshooting purposes,
try disabling or setting it to manual start and see if the error stops.
That will help confirm the source.

John

Simon wrote:

On registry I have found this:

REGEDIT4

[HKEY_CLASSES_ROOT\CLSID\{E9376CC6-121A-447e-81CF-D8BCC200007C}]
"AppId"="{653C5148-4DCE-4905-9CFD-1B23662D3D9E}"
@="Updates Class"

[HKEY_CLASSES_ROOT\CLSID\{E9376CC6-121A-447e-81CF-D8BCC200007C}\InProcHandler32]
@="Ole32.dll"

[HKEY_CLASSES_ROOT\CLSID\{E9376CC6-121A-447e-81CF-D8BCC200007C}\LocalServer32]
@="C:\\WINNT\\system32\\svchost.exe"

P.S.
I have the error when I'am connected on server via Terminal Services
Administrator mode.




Search the registry for {E9376CC6-121A-447E-81CF-D8BCC200007C} and find
out which service owns it. You will then be able to narrow your
troubleshooting to that service.

John

Simon wrote:


HI,
I heve W2K sp4 with terminal services installed and all security
updates installed too, but and DCOM error still logged on system log
many time.
This is the error:

Event Type: Error
Event Source: DCOM
Event Category: None
Event ID: 10010
Date: 3/20/2006
Time: 08:57:23 AM
User: Domain\administrator
Computer: ServerName
Description:
The server {E9376CC6-121A-447E-81CF-D8BCC200007C} did not register
with DCOM within the required timeout.

I have try to apply many KB from Microsoft support, but the error
still logged.
How to do I to solve this problem?

Thanks Simon.
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Similar Threads

DCOM Error; Event ID 10010 6
Event 10010 DCOM 3
repeated DCOM errors 0
Repeated WMI DCOM errors 0
DCOM PROBLEM 1
Event ID: 10010 <> Event Source: DCOM 3
DCOM Error 1
DCOM Error 1

Top