Submit a ticketCall us

AnnouncementsTHWACKcamp 2018 is here

2018 is the seventh year for THWACKcamp™, and once again we’ll be live October 17 – 18 with packed session tracks covering everything from network monitoring and management, to change control, application management, storage, cloud and DevOps, security, automation, virtualization, mapping, logging, and more.

Register for online sessions.

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

DCOM errors in event log on SAM server

Table of contents

Updated 07/09/2018

Overview

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

System section in Windows Event Log contains errors about DCOM error.

 

Environment

All SAM version

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 on 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

Tags

Classifications

Public