Submit a ticketCall us

Don’t fall victim to a ransomware attack
Backups are helpful, but sometimes that’s not enough to protect your business against ransomware. At our live webcast we will discuss how to protect against ransomware attacks with SolarWinds® Patch Manager and how to leverage log data to detect ransomware. Register now for our live webcast.

Home > Success Center > Network Performance Monitor (NPM) > Event 10028 "DCOM was unable to communicate with the computer"

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

Created by Jousseff Jaranilla, last modified by Brian.Jarchow on Jun 02, 2017

Views: 4,110 Votes: 4 Revisions: 30

Overview


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. 
 

 

Related Errors from DataProcessor.log:

Note: NPM 12 moved this to Collector\Logs\Collector.Service.Log

 

2016-05-12 15:43:56,722 [STP ProcessingPipeLine Thread #401] 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

 

2016-05-12 15:43:44,628 [STP ProcessingPipeLine Thread #400] 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

 

 

 

Environment

  • All versions of Orion products
  • All Solarwinds Products using WMI / RPC as polling Method. 
  • Windows Server 2008
  • Windows Server 2012
  • Windows Server 2016

Cause

Event 10028 DCOM error occurs 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.

Steps

1. Navigate to the directory from the Orion Server to verify nodes experiencing WMI challenge request (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.

    a. Type wbemtest in the run dialog box.

    b. Under Namespace change root\default to CIMV2 then click Connect.

    c. If a second dialog box appears, repeat step a.

    d. Click Enum Classes, select Recursive, and then click OK.

You should see a display of all the CIM objects

 

3. You can also double check stored credentials in Orion to check validity by going through the following steps:

   a. Go to Orion Web Console > Settings > Manage Windows Credentials.

 

4. Another Location for Credentials if you have SAM installed:

   a. Go to Orion Web Console > Settings > Sam Settings > Credentials Library. 

 

 

Last modified
10:01, 2 Jun 2017

Tags

Classifications

Public