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:WINDOWSsystem32DLLName.dll” -Embedding is not a valid Win32 application.
Happened while starting this command: “C:WINDOWSsystem32DLLName.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 ConfigurationWindows SettingsSecurity SettingsLocal PoliciesUser Rights AssignmentLog 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