Network Management

Network Sonar Discovery scheduled job fails due to UDT plugin issue

There are issues encountered when running either scheduled or manual Network Sonar Discovery jobs on the affected pollers.

First published date

6/21/2025 2:51 PM

Last published date

12/3/2025 12:22 AM

Overview

When you initiate a Network Sonar Discovery using an additional poller, all discovery jobs executed on that poller result in errors. No nodes are imported, and no discovered objects are added, even when the job is configured to automatically add them.

 

Core Business Layer Logs at C:\ProgramData\SolarWinds\Logs\Orion will show this error pointing to UDT Plugin:

ERROR SolarWinds.UDT.Common.Services.BaseWindsorModule -
(null)  Investigating type 'SolarWinds.UDT.BusinessLayer.Polling.UDTPolling' from assembly 'SolarWinds.UDT.BusinessLayer, Version=2024.4.0.0, Culture=neutral, PublicKeyToken=null' failed
Castle.MicroKernel.ComponentRegistrationException: Component SolarWinds.UDT.BusinessLayer.Polling.UDTPolling could not be registered. There is already a component with that name. Did you want to modify the existing component instead? If not, make sure you specify a unique name.

Product section

Orion Platform

Cause

The issue appears to be related to the UDT plugin used during Network Sonar Discovery. This has been identified as a known issue that affects certain APEs within the environment.

However, the root cause remains unclear, as some APEs function correctly, and the majority of network discovery jobs executed by the MPE are unaffected.

Resolution

To resolve this issue, please upgrade to SolarWinds Platform 2025.4 and above.  If upgrade is not possible. perform one of the workaround below:

Resolution 1:

If the nodes are on the same network as both the Additional Polling Engine (APE) and the Main Polling Engine (MPE), configure the node to use the MPE instead of the APE, especially if the APE is experiencing issues.

In some cases, manually running a network sonar discovery on the affected poller completes successfully. However, the issue occurs only during scheduled discovery job execution.

Resolution 2:

Adjust the discovery schedules to prevent jobs from running simultaneously or overlapping. For best results, ensure that each discovery job begins only after the previous one has had sufficient time to complete. This reduces the risk of conflict and improves the likelihood of successful job execution.

For example:

  • If one discovery job typically takes 1 hour to complete, schedule the next job to begin at least 15 minutes later.
  • Distribute discovery jobs across different times of day whenever possible.