Network Management

Agents can't connect to Agent Management Service

This article describes a scenario where Agents cannot connect to the Agent Management Service because the Agent Manage Service plugin has been disabled.

First published date

10/10/2018 12:25 PM

Last published date

2/3/2023 10:01 PM

Overview

This article provide some information about likely issues you may face during download/installation or operation/reprovision of SolarWinds Orion Agent.

When you try to download the Orion Agent from Web console, you receive following error:

Error getting agent installer for download. There was no response from the Agent Management Control Service located at "solarserv:17777"

During installation of Orion Agent, you see below error

IIS's httperr file is filling up the drive with the following errors: /solarwinds/agentmanagement/solarwinds/messaging/signalr/negotiate?clientProtocol=1.3 404 - NotFound.
BusinessLayerHost.log file contains the following error when starting the DPI Business Layer plugin:
ERROR SolarWinds.BusinessLayerHost.PluginInstanceAppDomain - Plugin "DPI Business Layer" failed to start. System.Runtime.Serialization.SerializationException: Unable to find assembly 'SolarWinds.DPI.BusinessLayer, Version=2.0.6.593, Culture=neutral, PublicKeyToken=null'.
AgentManagent.Service.log and AgentManagement.AMSProxy.log files are not getting updated.

Product section

Network Performance Monitor

Cause

Agent Management Service is not started or plugin disabled for some reason

Resolution

Resolution 1:
Launch Orion Service Manager and ensure "SolarWinds Agent Service" is running. If service is running but still having issue, then follow rest of the steps below.

Run Notepad as Administrator.
Open the following file:
\solarwinds\orion\agentmanagement\Solarwinds.AgentManagement.ServiceCore.dll.config
Find the following line:
<SolarWinds.BusinessLayerHost LoadPlugins="false">
Change it to the following:
<SolarWinds.BusinessLayerHost LoadPlugins="true">
Stop and start the Orion Module Engine service.

For later version of NPM or SAM you can follow the steps on the article below

https://support.solarwinds.com/SuccessCenter/s/article/Forcing-the-Business-Layer-to-load-plugins-in-a-separate-or-64-bit-process-in-NPM-12

Resolution 2:
Disable Agent Watchdog on affected Polling Engines:

1) Stop Orion Module Engine (BusinessLayer)
2) Go to ~/ProgramFiles/SolarWinds/Orion/AgentManagement
3) Backup SolarWinds.AgentManagement.Watchdog.dll.config
4) edit SolarWinds.AgentManagement.Watchdog.dll.config in way that you change element
<SolarWinds.BusinessLayerHost LoadPlugins="true" SeparateProcess="true" Support64="true" />
TO
<SolarWinds.BusinessLayerHost LoadPlugins="false" SeparateProcess="true" Support64="true" />
Difference is in LoadPlugins="true" vs. LoadPlugins="false"
5)Start Orion Module Engine
6) Wait 20 minutes and then try agent deployment or agent reprovision.

Disclaimer: Please note, any content posted herein is provided as a suggestion or recommendation to you for your internal use. This is not part of the SolarWinds software or documentation that you purchased from SolarWinds, and the information set forth herein may come from third parties. Your organization should internally review and assess to what extent, if any, such custom scripts or recommendations will be incorporated into your environment. You elect to use third-party content at your own risk, and you will be solely responsible for the incorporation of the same if any.