Initial Troubleshoot DCOM Errors 10000, 10001, 10002, 10003 and 10004


Continuing on the last topic about how to troubleshoot some of the most common DCOM Errors, a couple more of those below:

 

DCOM Event ID 10000

Description:

Unable to start a DCOM Server: {AppGUID}.

The error:

"C:\WINDOWS\system32\DLLName.dll" -Embedding is not a valid Win32 application.

Happened while starting this command: "C:\WINDOWS\system32\DLLName.dll" -Embedding

Cause

  • NTFS permissions are not setup properly.
  • The application or service is looking for a short file name or long file name.
  • Bug in the 3rd party or custom application.

Resolution

  • Check NTFS permissions (DCOM).
  • Check the path in the registry to make sure that short file name or long file name is being used.
  • Check for updates from the manufacturer.

 

DCOM Event ID 10001

Description:

Unable to start a DCOM Server: {AppGUID} as ./USERNAME.

The error:

"Access is denied. "

Happened while starting this command: %Path%\ExecutableName.exe /Processid:{ProcessGUID}

Cause

  • Permissions.

Resolution

  • Check the Check NTFS permissions (DCOM) .

 

DCOM Event ID 10002

Description:

Access denied attempting to launch a DCOM Server. The server is: {AppGUID}

Cause

  • App ID doesn't match.

Resolution

  • Check HKEY_CLASSES_ROOT for the AppGUID.
  • Check the DCOM Check NTFS permissions (DCOM) specific to the application.
  • Re-registering components.

 

DCOM Event ID 10003

Description:

Access denied attempting to launch a DCOM Server using DefaultLaunchPermission. The server is:{AppGUID}

Cause

  • Permissions.

Resolution

  • Check the DCOM Check NTFS permissions (DCOM) specific to the application.

 

DCOM Event ID 10004

Possible Descriptions:

DCOM got error "Logon failure: unknown user name or bad password. " and was unable to logon .\UserName in order to run the server: {AppGUID}.

DCOM got error "Logon failure: the user has not been granted the requested logon type at this computer." and was unable to logon to ComputerName in order to run the server: {AppGUID}

DCOM got error "A system shutdown is in progress." and was unable to logon to .\ComputerName in order to run the server: {AppGUID}.

DCOM got error "The referenced account is currently locked out and may not be logged on to. " and was unable to logon .\UserName in order to run the server: {AppGUID}

Cause

  • User rights of "Log on as a batch job" has been removed from Local/Domain.
  • Permissions.

Resolution

  • Add user rights under Computer Configuration\Windows Settings\Security Settings\Local Policies\User Rights Assignment\Log on as a batch job in the Local or Group Policy.
    Note: Make sure that the user account is not disabled or deleted.
  • Check the DCOM Check NTFS permissions (DCOM) specific to the application.

Hope that helps

Comments (2)

  1. Troy Reagan says:

    Hi,
    I started seeing the Event ID 10000 error about 2 weeks ago. The error seems to occur for any 32 bit ActiveX Servers (.exe) I run (I’m on 64-bit Windows 10). I’m able to run them from the command line fine and if I start them with the -Embedding option like it does when called from COM, the error goes away for that server when running our application. So it isn’t an invalid win 32 application and it shouldn’t be a registry issue since the application can create the object fine if the server is already running. As far as I know, I didn’t change any option that would affect them all so not sure what caused it. Any suggestions are appreciated.
    Thanks,
    Troy Reagan

    1. Hi Troy, unfortunately the “Event ID 10000” is a COM General Functionality failure, usually this means that there is a problem with the COM service.
      However, in this cases, there is not enough information available in the event message to provide a definitive recommendation to resolve the problem, this will need some more deep dive troubleshoot, and for that we will need more info.

Skip to main content