Network Management

Unable to reassign network discovery to additional polling engine

You are not able to assign the network discovery jobs to the additional polling engine as expected.

First published date

11/7/2023 4:05 PM

Last published date

11/5/2025 11:48 PM

Overview

Probing:
Confirm if you are able to create and assign network discovery jobs to the main polling engine.
Confirm if this only happens in one specific APE, and if you are able to assign a job to another poller.
Also confirm that the network firewalls are not blocking any ports needed using the Port Query tool. 


What error you should see in the logs: (Agent Logs)

WARN SolarWinds.Orion.Core.BusinessLayer.CoreBusinessLayerService - (null) Can't update scheduled jobs, JobScheduler is not running. - JobSchedulerException: PolicyExists: JobScheduler channel threw FaultException.
ERROR SolarWinds.Orion.Core.Common.JobEngine.JobScheduler - (null) PolicyExists: JobScheduler channel threw FaultException.
SolarWinds.Orion.Core.Common.JobEngine.JobSchedulerException: PolicyExists: JobScheduler channel threw FaultException. ---> System.ServiceModel.FaultException: Unable to connect to the remote agent with id '61704e0c-a038-4623-87bf-0a3b2b8a8ec4'


ServiceLogicalInstanceId OrionServerId ConnectionProperties
dwrccswpoll 3 {"Type":"SolarWinds.Orion.Core.JobEngine.Routing.ServiceDirectory.JobEngineRouterConnectionDescriptor, SolarWinds.Orion.Core.JobEngine.Routing, Version=2023.2.0.0, Culture=neutral, PublicKeyToken=null","Descriptor":"{\"ConnectionType\":\"Custom:JERouter\",\"ProxyType\":1,\"ProxyTarget\":\"61704e0c-a038-4623-87bf-0a3b2b8a8ec4\"}"}

 

Product section

Network Performance Monitor

Cause

Connection issue to a remote agent.
MPE/APE to port 17778 on Agent machine if Agent communication method is “Agent-initiated” or 
MPE/APE to port 17790 on Agent machine if Agent communication method is “Server-initiated”?

Resolution

Note: Please ensure there is a recent database backup prior to performing the steps below.

  1. Log in to the SolarWinds Platform Web Console.
  2. Navigate to Settings > All Settings > Service Manager.
  3. Stop all SolarWinds Platform Services on MPE and APE(s).
  4. Connect to your SolarWinds Platform server.
  5. Backup C:\ProgramData\SolarWinds\Orion\serviceDirectory.json file on the main polling engine and APEs.
  6. Delete serviceDirectory.json on MPE/APE.
  7. Open Database Manager from the SolarWinds Platform folder of the Start Menu.
  8. Select Add Orion Server. The SQL server and SolarWinds database appear on the left in bold.
  9. Right-click the database and select New query. Paste the following and click Execute:
-- Scripts are not supported under any SolarWinds support program or service.
-- Scripts are provided AS IS without warranty of any kind. SolarWinds further
-- disclaims all warranties including, without limitation, any implied warranties
-- of merchantability or of fitness for a particular purpose. The risk arising
-- out of the use or performance of the scripts and documentation stays with you.
-- In no event shall SolarWinds or anyone else involved in the creation,
-- production, or delivery of the scripts be liable for any damages whatsoever
-- (including, without limitation, damages for loss of business profits, business
-- interruption, loss of business information, or other pecuniary loss) arising
-- out of the use of or inability to use the scripts or documentation.

DELETE FROM ServiceDirectoryEntries
  1. Try assigning a network discovery to the affected additional polling engine.


In the database manager, you can execute the query "DELETE FROM ServiceDirectoryEntries" or you may use the SQL Server Management Studio app in the SQL server itself to execute the query,