Network Management

Event 10028 "DCOM was unable to communicate with the computer"

This article provides information regarding the root cause of Event 10028, "DCOM was unable to communicate with the computer," and how to address this issue or verify that it is a genuine error. 

First published date

10/30/2018 4:51 PM

Last published date

6/11/2025 12:28 AM

Overview


These DCOM errors also create Ephemeral Port Exhaustion and a 'work around'/'band aide' fix can be applied by Tweaking Windows Server performance to prevent port exhaustion when using Orion modules. 

This problem creates many server connection issues including interrupting communication from the SolarWinds Platform Server to the SQL Server. 

Here is an example of the DCOM error in the Event Log:

image.png

Related Errors from C:\ProgramData\SolarWinds\Collector\Logs\Collector.Service.log

ERROR DataPreProcessing - Processing result: PollerResultWrapper: PollerType=V.Status.WMI.Windows, NetObject=V:79 ErrorCode=800705AF, ErrorMessage= Scope: IPAddress\root\CIMV2[\chcrr\svc_chcsw] ErrorCode: 0x800705AF
-------------------------------------------------------------------------
ERROR DataPreProcessing - Processing result: PollerResultWrapper: PollerType=N.Memory.WMI.Windows, NetObject=N:222 ErrorCode=800705AF, ErrorMessage= Scope: IPAddress\root\CIMV2[\chcrr\svc_chcsw] ErrorCode: 0x800705AF

Product section

Orion Platform

Cause

Event 10028 DCOM error occurred when the WMI request failed to communicate with a remote node due to Invalid Credentials or an Invalid WMI Namespace on the Target Device. As a result, an event is being logged automatically on your Application Server's Event Logs.

Resolution

  1. Navigate to the directory from the SolarWinds Platform Server to verify nodes experiencing WMI challenge requests (C:\ProgramData\Solarwinds\Collector\Logs)
  2. Look for the CollectorService.log and manually search the nodes in question using the keyword CIMV2.
  3. To verify the Error is genuine, you can perform a Wbemtest to verify if the credentials set are valid.
  4. Type WBEMTest in the run dialogue box.
  5. Under Namespace, change root\default to root\CIMV2, then click Connect.
  6. If a second dialogue box appears, repeat step 4.
  7. Click Enum Classes, select Recursive and then click OK. You should see a display of all the CIM objects.
image.png
  1. You can also double-check stored credentials in the SolarWinds Platform to check validity by going through the following steps:
    1. Go to SolarWinds Platform Web Console > Settings > Manage Windows Credentials.
  2.  Another Location for Credentials if you have SAM installed:
    1. Go to SolarWinds Platform Web Console > Settings > Sam Settings > Credentials Library. 
  3. Check the SAM Application if there is a whole application that displaying an unknown.
    1. Resolve the credential issue of this Unknown Application
    2. Remove it if this application is not used on monitoring