Network Management

Adding Agent to additional poller fails with connection Agent Management Control Service located at 17777

This article describes an issue that generates an Agent Management Control Service error when using the agent polling method to monitor an Additional Polling Engine. Error: Orion.AgentManagement.Agent.ValidateDeploymentCredentials failed, check fault information. There was no response from the Agent Management Control Service.

First published date

6/17/2019 5:09 PM

Last published date

8/5/2023 8:07 PM

Overview

When you add a node to monitoring, you can choose which polling engine is assigned to the node. If you are using the agent polling method, the method requires you to install the agent on the target server.

When you add a node to monitoring using the agent polling method on an Additional Polling Engine, the following Agent Management Control Service error message displays: 

Orion.AgentManagement.Agent.ValidateDeploymentCredentials failed, check fault information. There was no response from the Agent Management Control Service located at "Node:17777".

Product section

Orion Platform

Cause

The main server is unable to reach the Additional Polling Engine using TCP port 17777 due to a network-related issue (such as DNS, firewall, and so on).

Resolution

Reach out to your network/system administrator to ensure that the main server can reach the Additional Polling Engine

  • The main server should be able to resolve the Additional Polling Engine hostname to a valid IP address.
  • The main server should be able to connect to the Additional Polling Engine using TCP 17777.

(Optional) Add an entry in the main server hosts file for manual hostname resolution

  1. On your main server, navigate to:
    C:\Windows\System32\drivers\etc
  2. Open the hosts file in a text editor (such as Notepad). 
  3. Add a line in the hosts file with the IP address followed the additional polling engine's hostname.
  4. Save and close the file.
 

Disable Agent Watchdog in affected poller

Important ! Please make this modification on all affected pollers.  This is a short-term workaround.  Please file a SolarWinds Support case to properly root cause the problem.  
  1. Stop SolarWinds Orion Module Engine
  2. Navigate to
    • C:/Program Files (x86)/SolarWinds/Orion/AgentManagement (for 2020.2.6 and below)
    • C:/Program Files/SolarWinds/Orion (for 2022.3 and above)
  3. Backup SolarWinds.AgentManagement.Watchdog.dll.config
  4. Modify SolarWinds.AgentManagement.Watchdog.dll.config (in RED)
<SolarWinds.BusinessLayerHost LoadPlugins="true" SeparateProcess="true" Support64="true" />
TO
<SolarWinds.BusinessLayerHost LoadPlugins="false" SeparateProcess="true" Support64="true" />
  1. Start SolarWinds Orion Module Engine
  2. Wait 20 minutes and try agent deployment from that poller and let us know the result