Information: Forum is in read-only mode
For details and other support options see

Event ID:10010 "Server did not register..."

Discuss Windows Event Log events. What they mean, what they tell you about your machine's security ... and whatever questions else you have.

Moderator: alorbach

Google Ads

Event ID:10010 "Server did not register..."

Postby Guest » Sat Oct 25, 2003 2:03 pm

The server %1 did not register with DCOM within the required timeout.

I have been getting this lately. Soon following that, most if not all of the services I have running die leaving the computer in a nonworking state. I have to reboot and then everything turns out just fine.

I am using Windows XP Pro. If you need any other details I can answer those.

My email is zentraedi AT verizon DOT net

E-mail me with any suggestions.

The server did not respond

Postby dozi » Sat Oct 25, 2003 4:42 pm

I get the same, just started happening within last week and get memory errors too

Postby alorbach » Mon Oct 27, 2003 10:26 am


do you both have the latest security patches from Microsoft installed?
Take a look to this site, or run Windows Update: ... indows.asp

There are a fwe dcom exploits out which can cause these error's as a side effect.
Site Admin
Posts: 1627
Joined: Thu Feb 13, 2003 11:55 am

Postby Guest » Fri Oct 31, 2003 4:35 am

I have the most recent Windows Update patches. Yet I still get it.

Postby Guest » Sun Nov 02, 2003 8:34 pm

Hi, just found this forum.

I don't know if this will help but I kept getting the same error so I booted into safe mode (w/o networking), did nothing, shut down, restarted, and I'm back to normal.

Good luck.

Anonymous wrote:I have the most recent Windows Update patches. Yet I still get it.

DCOM Event 10010

Postby Robert_J_Sherman » Tue Nov 11, 2003 9:12 pm

Well, it's nice to know I'm not alone.

I've tried the various MS KB articles/suggestions - re-installed IE6/OE6 and removed MSN 4.7 - none of these solved the problem.

I've scratched my head till it's raw.

Anyway, at moment it appears to be somehow related to IE, and how I connect... if I manually dial using the "connect to...." - the DCOM time occurs immediately (okay, it takes 10 minutes before I can do anything else), if I dial in by opening IE, then my problem doesn't start until I either 1) open another app (like outlook, or eudora) or 2) I attempt to disconnect... in which case, I wait about 10 minutes before I can go back to normal operation(s).

All other aspects of the system run smoothly.

I'll try guest 3's suggestion of booting into safe-mode w/out networking.. see if that does anything fer me.

I dunno about the rest of you, but it'd be real nice if this error would tell us "what" application is the culprit -- in terms that one could actually understand... class id's are not plain text.

Postby Robert_J_Sherman » Thu Nov 13, 2003 6:52 pm

Tried the safe-mode, didn't seem to resolve it....

It has slowed somewhat, only happening about once a day, instead of every time I try to establish a connection.

I'm still leaning toward Symantec LiveUpdate as the Problem... symantec swears it's not.. but the server class id referenced in the event message, nearly always points to liveupdate.

Disabling it, didn't help either.

really a bit on the befuddled side here.

Postby Guest » Thu Nov 13, 2003 7:11 pm

I don't know how exactly to do it, but having you tried disabling DCOM?

Postby alorbach » Fri Nov 14, 2003 9:34 am


I guess all you guys connect directly to the internet, right?
And do you all use Windows 2000 or XP?
Site Admin
Posts: 1627
Joined: Thu Feb 13, 2003 11:55 am

Error: The server %1 did not register with DCOM within the r

Postby » Fri Aug 27, 2004 8:43 pm

Has anyone found a resolution to this problem???

Source: DCOM
Event ID: 10010
Description: The server {08B0B2D8-3FB3-11D3-A4DE-00C04F610189} did not register with DCOM within the required timeout.
we are getting it on a box running SQL Server.

Postby therget » Mon Aug 30, 2004 9:03 am

Hi all,

I found a Microsoft Knowledge Base Article concerning the DCOM 10010 Error :

Microsoft Knowledge Base wrote:
DCOM Clients Cannot Create Objects

View products that this article applies to.
This article was previously published under Q187146
IMPORTANT: This article contains information about modifying the registry. Before you modify the registry, make sure to back it up and make sure that you understand how to restore the registry if a problem occurs. For information about how to back up, restore, and edit the registry, click the following article number to view the article in the Microsoft Knowledge Base:

256986 Description of the Microsoft Windows Registry


Distributed Component Object Model (DCOM) client programs that run inside Terminal Server sessions other than the console cannot create objects of classes implemented inside DCOM servers running as Terminal Server services.

You may also receive occurrences of event ID 10010 from DCOM in the Event Viewer with the following description:

The server <clsid> did not register with DCOM within the required timeout.


You may also receive the following error message:
CoGetClassObject failed - Server Execution failed CO_E_SERVER_EXEC_FAILURE 0x80080005


This behavior is because those object classes are considered as user globals by DCOM and Terminal Server.

However, DCOM and Terminal Server provide the ability to register DCOM classes as system globals. But, in the case of classes implemented in services, they should be considered as system globals, unless they had been explicitly registered as user globals.


WARNING: If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk.

To explicitly register a DCOM class as a system global, use the following steps:

1. If it does not exist, create the following registry key:
HKLM\Software\Microsoft\Windows NT\CurrentVersion\Terminal Server\Compatibility\CLSID

2. Create a subkey with {CLSID} as its name, where the CLSID is the class identifier of the DCOM class that is to be a system global. For example, a subkey would be:


3. Under the above subkey, create fSystemGlobalClass as the value name with a REG_DWORD type and set its value data to 1.

Or, you can upgrade to Microsoft Windows 2000 Server with Terminal Services, which does not have the same restriction.


Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.


To reproduce this, use the DCOM sample named "ATLDRAW" provided with the ActiveX Template Library (ATL).

Please notice that you use the registry editor at your own risk.

Timm Herget
Frequent Poster
Posts: 79
Joined: Thu Dec 18, 2003 12:42 pm

DECOM 10010 Error

Postby Jim D » Tue Sep 07, 2004 2:32 pm

Frustrated by the same DCOM error. Has anyone resolved it? It has only begun happening in the last few weeks, so I suspect the latest Critical Updates. Has anyone found how to stop it?
What about "disabling" the DCOM service?
Jim D

DCOM 10010 error

Postby MACAUS » Wed Sep 15, 2004 11:40 am

Try to identify in the registry what the CLSID string points to. From experience most happen to be MS Messenger related and they mostly appeared after one of the recent MS Updates on XP Pro machines. Have downloaded the MS Messenger and run the install and it fixed the issue.

MS claims that the DCOM object was not loaded properly and the reinstall just reregistered the DCOM server.

Hope this helps you out.

Postby Guest » Fri Oct 01, 2004 6:07 pm

Hi, I seem to be getting the same DCOM error.

DCOM got error "This service cannot be started in Safe Mode " attempting to start the service EventSystem with arguments "" in order to run the server:

When it happens, it actually switches off my pc, and it sometimes happens every few minutes, somtimes after an hour or so.
I have a 3200 barton processor running XP home. My connex is 1mb cable.

Ive tried reinstalling messenger, but no use.
Anyone help?

Postby Guest » Sat Oct 02, 2004 12:41 pm

^^^^ That was actually a changed one i got after starting in safe mode.
The usual one is;

The server {9F92FFA3-40D1-475A-9323-A39C705DAB86} did not register with DCOM within the required timeout.


Google Ads


Return to Windows Events

Who is online

Users browsing this forum: No registered users and 2 guests