DCOM error on Server 2008R2


  • We are getting this error in our event logs - what is it and how to I correct it:

    og Name:      System
    Source:        Microsoft-Windows-DistributedCOM
    Date:          11/20/2012 1:04:56 PM
    Event ID:      10010
    Task Category: None
    Level:         Error
    Keywords:      Classic
    User:          N/A
    Computer:      A4HS03.A4HS-DOM.local
    The server {23B67C54-D9B2-11D2-A045-0080C76912DE} did not register with DCOM within the required timeout.
    Event Xml:
    <Event xmlns="">
        <Provider Name="Microsoft-Windows-DistributedCOM" Guid="{1B562E86-B7AA-4131-BADC-B6F3A001407E}" EventSourceName="DCOM" />
        <EventID Qualifiers="49152">10010</EventID>
        <TimeCreated SystemTime="2012-11-20T18:04:56.000000000Z" />
        <Correlation />
        <Execution ProcessID="0" ThreadID="0" />
        <Security />
        <Data Name="param1">{23B67C54-D9B2-11D2-A045-0080C76912DE}</Data>

    I searched the GUID in the registry and it came back to : HKEY_CLASSES_ROOT\csimSecurityDesktop.SecurityDesktop

    Monday, December 10, 2012 12:46 AM


All replies

  • check out this link:

    Every second counts..make use of it.

    Monday, December 10, 2012 3:06 AM
  • Thank you for your reply.......but, I need a little more help :)  I followed the article you referenced, but cannot find the refence to the csimSecurityDesktop.SecurityDesktop.....and not sure what the correct permission would be when I find it -


    Monday, December 10, 2012 2:40 PM
  • Did you install any driver or hardware recently?

    Do you got any applications or hardware that uses  or reference to DCOM?

    I guess it has nothing to be alarmed, it could only be some applications didn't work properly.

    if you want to dig some more check out this link from technet

    DCOM Security Enhancements

    What does DCOM do?

    The Microsoft Component Object Model (COM) is a platform-independent, distributed, object-oriented system for creating binary software components that can interact. The Distributed Component Object Model (DCOM) allows applications to be distributed across locations that make the most sense to you and to the application. The DCOM wire protocol transparently provides support for reliable, secure, and efficient communication between COM components. For more information, see "Component Object Model" on the Microsoft Web site at

    Who does this feature apply to?

    If you only use COM for in-process COM components, this section does not apply to you.

    This feature applies to you if you have a COM server application that meets one of the following criteria:

    • The access permission for the application is less stringent than the launch permission that is necessary to run the application.
    • The application is usually activated by a remote COM client without using an administrative account.
    • The application is only meant to be used locally. This means you can restrict your COM server application so it is not remotely accessible.

    Every second counts..make use of it.

    Tuesday, December 11, 2012 1:00 AM
  • Hi,

    Thank you for the post.

    “I searched the GUID in the registry and it came back to : HKEY_CLASSES_ROOT\csimSecurityDesktop.SecurityDesktop” - Please check if all the users unable to establish an RDP session? If yes, does restart server resolve this issue? You may install the following hotfix and see if it works.


    Nick Gu - MSFT

    Wednesday, December 12, 2012 8:15 AM
  • Thank you Nick - no issues with RDP - all users connect/disconnect with no issues.......
    Friday, December 14, 2012 1:33 AM
  • Hi,

    Thank you for the update.

    Do you have any update about Cguan’s question? Is there any other component involve in event id 10010?


    Nick Gu - MSFT

    Monday, December 17, 2012 2:10 AM
  • Hello Nick - no hardware or software updates......this error has been there since deployment of the server.  No other component involved..... 
    Monday, December 17, 2012 2:28 AM
  • HI,

    Thank you for the update.

    As far as I know, DCOM 10010 has no harm to your system. If there is no other error message or unexpected behavior, you may ignore this event id.

    For more details about how DCOM 10010 is logged, you can reference below article:

    Why my DCOM service reports 10010 error


    Nick Gu - MSFT

    Tuesday, December 18, 2012 2:15 PM