Initial Troubleshoot DCOM Errors 10010 and 10016

Yes, that's true, today I decided to write something about some two typical errors that we see on DCOM and most of the times drives some of us a little bit mad.
Yes, that's right DCOPM is still a thing in our bright days of could computing and IoT.

So, some of the most popular errors on the DCOM World are the below (they usually also like to hang out together), see how to tackle them.

DCOM Event ID 10010
The server {AppGUID} did not register with DCOM within the required timeout.

Typical Causes

  1. NTFS permissions have been locked down.
  2. Dll's have become unregistered (check to see if they are corrupted).
  3. The service failed to start or is at either starting/Stopping state (hung).
  4. An application tries to restart the service repeatedly.
  5. Bug in the 3rd party or custom application.
  6. RPC service has "Allow Service to Interact with Desktop" checked.
  7. A dependent service starts before the service throwing the error.
  8. Permission of application is set incorrectly.

Usual Resolution

  1. Check the Check NTFS permissions (DCOM) .
  2. With the AppGUID, find what application it is and try Re-registering exe's (DCOM)
  3. Stop and try restarting the service.
  4. Disable 3rd party services and startup items, go thru the process of elimination.
  5. Check for an update from the software vendor.
  6. Uncheck the "Allow Service to Interact with Desktop" within the RPC service and reboot.
  7. KB193888 How to Delay Loading of Specific Services.
  8. Check the DCOM Check NTFS permissions (DCOM) specific to the application.


DCOM Event ID 10016

The application-specific permission settings do not grant Local Launch permission for the COM Server application with CLSID {AppGUID} to the user SID (UserSID).
This security permission can be modified using the Component Services administrative tool.

Typical Causes

  1. Network service account does not have permissions in local or GPO.
  2. Script debugging is disabled in Internet Explorer.

Usual Resolution

  1. Add the "Network Service" account with full permission to Computer Configuration\Windows Settings\Security Settings\System\ Services\ServiceName
  2. Open Internet explorer\Tools\Internet Options\Advance tab\Uncheck Display notification about every script error\Check Disable Script Debugging IE\Check Disable Script debugging (Other)\Click ok.

Hope that helps

Comments (1)

  1. Johannes says:

    Hey José!

    It would be nice to know why this error comes back everytime Microsoft decides to desiminate a new Windows 10 drop.

Skip to main content