NetCrunch Knowledge Base

How-tos, troubleshooting and answers about NetCrunch.

Diagnosing DCOM error messages and how to resolve them (12.x-13.x)

I receive tons of DCOM events being logged for NetCrunch against almost every single Windows machine. The events are recorded for the WMIrequester that informs about insufficient authentication level for DCOM. Error message I get is as follows: DCOM was unable to communicate with the computer COMPUTER using any of the configured protocols while activating CLSID {ID}. How to deal with this issue?

Applies to 13.x 12.x

Verify the DCOM setting on monitored Windows nodes that report DCOM issues. Check it also on the Windows machine where NetCrunch Server is installed:

  1. Click Start, type dcomcnfg in the Start Search bar, and press Enter.
  2. Double-click Component Services.
  3. Double-click Computers.
  4. Right Click on My Computer.
  5. Click on the Default Properties tab.
  6. Ensure that Enable Distributed COM on this computer is checked; the Default Authentication Level is set to Connect, and Default Impersonation Level is set to Identify. If you made any changes to correct the settings, click Apply.
  7. Now click on the COM Security tab.
  8. Under Access Permissions click Edit Default.
  9. Ensure that the Self, System, and Administrator have Local Access set to Allow; and that the Self and Administrator have Remote Access set to Allow. If any of these users are missing, please add them. If any of these settings are not checked please set them. Make the necessary changes, and click OK to close this window.

These settings should be applied to the account used for monitoring Windows nodes.

NetCrunch. Answers not just pictures

Maps → Alerts → Automation → Intelligence

See NetCrunch in action Check pricing