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) > Event 10009. DCOM was unable to communicate with the computer

Event 10009. DCOM was unable to communicate with the computer

Created by Aileen de Lara_ret, last modified by Erin Stenzel on Sep 09, 2016

Views: 587 Votes: 0 Revisions: 6

Overview

This article provides brief information and steps to resolve the following error when you upgraded to SAM 5.0.0:

DCOM was unable to communicate with the computer ***.**.*.***. using any of the configured protocols.

Environment

SAM version 5.0.0 and above

Resolution

1. Edit the C:\Program Files (x86)\SolarWinds\Orion\APM\SolarWinds.APM.Probes.dll.config file.
2. Find the <wmisettings/>section and change the ConnectOptions from BothAutoCorrectedFirst to Default:

 <!-- WmiSettings
    ConnectOptions:
       Default - use IP address
       OnlyAutoCorrected - use only IP address + "." (if IP address is IPv4 address)
       BothAutoCorrectedFirst - try to use AutoCorrected version first and then Default version
       BothDefaultFirst - try to use Default version first and then AutoCorrected version
    DoReverseLookupWhenFailed - if "true" then the Reverse DNS Lookup is executed and the log file contains IP address list of target machine
  -->
  <WmiSettings Retries="3" WaitToRetry="0:00:10" ConnectOptions="Default" DoReverseLookupWhenFailed="true"/>

3. Restart the SolarWinds Job Engine v2 service to apply the changes.

Note: These steps can also be used for all additional pollers (if you have any).

 

 

 

Last modified
12:34, 9 Sep 2016

Tags

Classifications

Public