Submit a ticketCall us

Announcing NCM 7.7
With NCM 7.7, you can examine the rules that make up an access control list for a Cisco ASA device. Then you can apply filters to display only rules that meet the specified criteria, order the rules by line number or by the hit count, and much more.
See new features and improvements.

Home > Success Center > Server & Application Monitor (SAM) > DCOM errors in event log on SAM server

DCOM errors in event log on SAM server

Updated July 27th, 2016

Overview

This article provides brief information and steps to resolve the following error:

DCOM was unable to communicate with the computer <ip address>  ***.**.*.***. using any of the configured protocols. Filling up the System event log errors on the Solarwinds application server. 

Environment

SAM v6.2

Cause 

This can be due to a WMI component in an application template being deployed against a Linux node. Alternatively
on Windows nodes, the poller may be unable to poll due to insufficient access/High physical memory, etc… on the remote node. The actual error is caused by the remote node not being able to respond to WMI-get requests.

Resolution

  1. Go to Edit Nodes for the node that is in the error message in the event log using the IP. 
    • If the node is registered as a server name you may need to look up the name to search for using the ip address in a ping command. 
  2. On the node look for applications that are grey or have a status of known. click into the application and then click edit application. Look at the components that show unknown and are WMI components. If these are deployed on a Linux then remove from the assigned node.  
    • This can be done by going to settings -> SAM Settings -> manage applications finding the application template and clicking on the check box for the application -> clicking delete. 

 

Last modified
07:56, 23 Mar 2017

Tags

Classifications

Public