Network Management

Solarwinds Module Engine service crashes with AgentManagement error

This article describes how to resolve the issue of the Business layer crashing with an error such as SolarWinds.AgentManagement.ServiceCore.dll.config - ProcessID: 4328 doesn't exist anymore Node: The ProcessID may be a different number.

First published date

6/17/2019 7:14 AM

Last published date

8/5/2023 7:55 PM

Overview

  • Agent Management Service (AMS) continuously fails in the business layer located at C:\ProgramData\Solarwinds\Logs\Orion\BusinessLayerHost.log. 
  • Each time all the plugins start, but then the agent service plugin fails.
  • The files should end with "All plugins Started"
Business layer crashing will also cause the web console (If this is on Main Poller) to load very slowly or fail to load.

The Business Layer log file contains entries such as: 
2019-06-10 15:47:32,186 [7] INFO  SolarWinds.BusinessLayerHost.BusinessLayerHostService - All plugins started
2019-06-10 15:54:32,497 [Scheduler] ERROR SolarWinds.BusinessLayerHost.PluginInstanceSeparateProcess - Instance C:\Program Files (x86)\SolarWinds\Orion\AgentManagement\SolarWinds.AgentManagement.ServiceCore.dll.config - ProcessID: 4328 doesn't exists anymore
2019-06-10 15:54:32,497 [Scheduler] ERROR SolarWinds.BusinessLayerHost.PluginManager - Child process for C:\Program Files (x86)\SolarWinds\Orion\AgentManagement\SolarWinds.AgentManagement.ServiceCore.dll not found and will be restarted.
2019-06-10 15:54:32,497 [Scheduler] INFO  SolarWinds.BusinessLayerHost.PluginInstanceSeparateProcess - Initialize plugin C:\Program Files (x86)\SolarWinds\Orion\AgentManagement\SolarWinds.AgentManagement.ServiceCore.dll.config - ProcessID: 4328

The following error may also be found in the AgentManagement.Watchdog.log at C:\Programdata\Solarwinds\Logs\AgentManagement: 
2019-06-10 15:53:40,228 [3] ERROR SolarWinds.AgentManagement.Messaging.Contract.MessagingServiceProxy - Messaging Service endpoint 'net.pipe://localhost/SolarWinds/AgentManagement/Messaging' was not found. There was no endpoint listening at net.pipe://localhost/SolarWinds/AgentManagement/Messaging that could accept the message. This is often caused by an incorrect address or SOAP action. See InnerException, if present, for more details.
2019-06-10 15:53:40,228 [13] WARN  SolarWinds.AgentManagement.Messaging.Contract.MessagingServiceProxy - Connection to messaging service at 'net.pipe://localhost/SolarWinds/AgentManagement/Messaging' faulted. Running reconnection.
2019-06-10 15:53:40,228 [13] ERROR SolarWinds.AgentManagement.Messaging.Contract.MessagingServiceProxy - Messaging Service endpoint 'net.pipe://localhost/SolarWinds/AgentManagement/Messaging' was not found. There was no endpoint listening at net.pipe://localhost/SolarWinds/AgentManagement/Messaging that could accept the message. This is often caused by an incorrect address or SOAP action. See InnerException, if present, for more details.

Product section

Orion Platform

Cause

This issue occurs due to Watchdog DLLs seem to be causing issues for the application.

Resolution

  1. Stop SolarWinds Platform Services. 
  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. Back up the files SolarWinds.AgentManagement.Watchdog.dll and SolarWinds.AgentManagement.Watchdog.dll.config.
  4. Delete SolarWinds.AgentManagement.Watchdog.dll and SolarWinds.AgentManagement.Watchdog.dll.config.
  5. Start the services.
After starting services open C:\ProgramData\Solarwinds\Logs\Orion\BusinessLayerHost.log and confirm the Agent Management plugin is not failing and the file ends with "All plugins started".