none
Event ID:- DCOM 10010 triggered on Windows 2003 X64 RRS feed

Answers

  • FOR DCOM Event ID 10010

    POSSIBLE CAUSES:

    • NTFS permissions have been locked down.
    • Dll's have become unregistered (check to see if they are corrupted).
    • The service failed to start or is at either starting/Stopping state (hung).
    • An application tries to restart the service repeatedly.
    • Bug in the 3rd party or custom application.
    • A dependent service starts before the service throwing the error.
    • Permission of application is set incorrectly.

    Description :- The server {639F725F-1B2D-4831-A9FD-874847682010} did not register with DCOM within the required timeout.

    We can find the assisted file directory from the below registry location.

    HKEY_CLASSES_ROOT\CLSID

    File extension end with “.EXE” files we need to go to that file location and reregister the affected file.

    Command:-  <filename> /regserver

    File extension end with “.DLL” files we can reregister with below command

    Command:- regsvr32 <filename>

    Please follow the above steps and monitor the server for some time. If we get new “AppGUID” please do the same steps and monitor.

    NOTE : The errors that are listed above are very generic errors and can come in a lot of situations. The purpose of this step is to eliminate one basic cause which we come across a lot of times. Doesn't fix the issue for us, then we need to look further.

    • Marked as answer by Joanstan Wednesday, March 27, 2013 6:47 AM
    Wednesday, March 27, 2013 6:46 AM