In deployments with additional polling engines (APEs), attempting to integrate the SolarWinds Platform with DPA would install the DPA Business Layer on the APE. This caused problems with the DPA integration, including:

• Application relationships added on the Manage Client Application Relationships page were automatically removed.

• Integration fails with the message There was an error when trying to enable the integration with the DPA server: Establishing federation with jSWIS failed.

• Attempting to add a DPA server returns the message Cannot find a DPA server at this address or port. Check your DPA server details and network connection.

When you run a report that queries the SolarWinds log database, the results of the query are shown instead, not the message Query is not valid.

In a large, complex environment, network configuration management jobs and inventory jobs run as expected.

Network configuration management jobs no longer make unnecessary APE license checks, which were causing the jobs to run slowly.

Inventory collection was updated to prevent database blocks, which were affecting performance.

A vulnerability that could expose a password has been fixed.

A misspelled word in INFO messages in the NCM.Collector.Jobs_[*].log file has been corrected.

The Config Details page shows the downloaded time based on the SolarWinds Platform time zone, not UTC time.

When an inventory job retrieves a large Flash Size value, it records the value correctly and no longer returns the following error:

Arithmetic overflow error converting expression to data type int.

Real Time Change Notification works as expected when the IP address provided to it is not the primary IP address for the node.^*

In 2023.2, the default timeout value for SWJobEngineWorker2x64.exe was increased from 20 minutes to 2 hours. In deployments with a large number of jobs that did not finish before the 2-hour timeout, memory usage increased significantly. To prevent this issue, the default timeout value has been decreased to 20 minutes.

When the SolarWinds Platform is configured to use Windows authentication, running interface percentile traffic reports no longer returns an error.

If an interface name includes special characters, the special characters are no longer escaped on the Interfaces with High Percent Usage (no paging) resource. This behavior was preventing database maintenance from running as scheduled.

The load time for the Interface Availability widget has been significantly decreased.

By default, network discovery enables all pollers on a device. So, if a topology poller is disabled on the List Resources or Manage Pollers page, it is enabled again when network discovery runs. A new advanced configuration option is available to enable you to override this default behavior. If do not want certain topology pollers to be enabled when network discovery runs:

1. Open the Advanced Configuration options page by pasting the following into your browser URL field after the hostname or IP address:

   /Orion/Admin/AdvancedConfiguration/Global.aspx

2. Under Topology, locate the PollersDiscoveryBlackList field.

3. Enter a comma-separated list of topology pollers that should not be enabled when network discovery runs.

Out-of-the-box Switch Stack alerts can be copied and edited, and they are triggered as expected.

Universal Device Poller gauges load without errors and performance is improved.

If application data is corrupted, the Manage Applications and Service Ports page no longer attempts to list the applications. Corrupt data does not prevent the page from opening with the following message:

Unexpected Website Error
Sequence contains no elements

Additionally, a daily maintenance task detects and removes any corrupt application data.

If a user without permission to view NetFlow data attempts to access a NetFlow page, permissions are evaluated and the Restricted page message is displayed before the page loads. The page is no longer loaded and then hidden, and attempts to refresh the page do not affect performance.

A change to the NetFlowInterfaceSources_Metadata table in the SolarWinds Platform database prevents deadlocks in environments with a large number of VMware devices.

If a deployment includes more than one application template with the same name, the Configuration Wizard no longer fails with the following error:

Database configuration failed: Error while executing script- Subquery returned more than 1 value.

The SolarWinds Platform Web Console no longer becomes unresponsive or stops functioning due to missing keys in the cloud monitoring resource file.

On the Node Details Summary page, when you click Real Time Event Viewer and then click the Message column for an event, the Message Details popup opens as expected.

When you add a node with Microsoft SQL Server 2022 deployed, AppInsight for SQL is discovered.

During upgrades data from old tables is migrated successfully and the obsolete tables are removed. In a previous version, incomplete data migration could cause issues such as:

• The Configuration Wizard failed with the message Invalid object name 'APM_ComponentStatus_Hourly.

• The SolarWinds Platform database size decreased significantly.

• The Application Component Details page did not consistently display messages.

If the Configuration Wizard fails during an upgrade, attempting to rerun the wizard no longer fails with the message Error while executing script- There is already an object named 'CLM_CloudJobSettings' in the database.

When a problem occurs with the API poller, the following message was improved to provide more information about the cause of the problem:

Index was outside the bounds of the array.

When a node is deleted or unmanaged, Application Dependency Mapping (ADM) polling does not continue for that node. In previous versions, continuing to poll a deleted or unmanaged node for ADM data caused the ADM_ProcessingQueue table to become very large.

Long status messages associated with an application monitor are displayed correctly after an upgrade.

Alerts on API Pollers that should be triggered when the response time exceeds a threshold are no longer triggered when the response time is below the threshold.

If ADM polling is disabled for the SolarWinds Platform, the node detail page does not display the Application Dependency Polling Enabled check box.

If AppInsight for IIS runs for long periods, the APM_IisBb_Request_Detail table no longer grows without limits, causing performance issues.

The CreateApplication verb in SWIS for the AppInsight for SQL template now works when you are using a remote node and database. Issues with credentials and connection testing have been resolved.

The default poll no longer fails when more than one array is in a Nimble cluster.

The Vserver Status widget and the Vservers on this Cluster widget now show the same Vserver capacity data.

The Ethernet Ports Used Over Time now shows data for the selected time period instead of only the data for the current day.

When a wireless node is discovered with UDT port monitoring enabled and devices from the node are added to the Watchlist, the Watchlist widget no longer displays type conversion errors such as:

Conversion failed when converting the nvarchar value 'Vanguard_WLC' to data type int.

The Port Details widget now displays the MAC address, IP address, or Hostname for all devices.

The All User Log Ins widget displays data about the currently open endpoint, not the first endpoint that was opened.

The Port Details widget displays IP addresses even if the VLAN port is not monitored.^*

When a node uses automatic private IP addressing (APIPA), the vendor and machine type are reported correctly.

Database maintenance no longer fails with the following message:

SolarWinds.Data.DatabaseMaintenance.StandardTableHandlerDAL - Failed to execute procedure: VIM_dbm_Clusters_ComputeDiskDepletion System.Data.SqlClient.SqlException (0x80131904): Arithmetic overflow error converting expression to data type bigint.

Cursor is not open.

The bulk insert query no longer runs slowly and causes performance issues on the database.

The Calls by Region widgets display the correct data.

IP SLA operations function correctly, and the ipsla.bussiness.layer log file no longer includes the message Violation of PRIMARY KEY constraint.

The FTP server is no longer filled with failed files, and VoIP views displays call manager information correctly.

After a call manager is removed, any associated CDR files are no longer processed, which prevents putting an unnecessary load on the FTP server.

Call managers are polled only by the assigned polling engine, not by all polling engines.

When CDR files for different call managers are stored in separate folders on the FTP server, CDR files for all call managers are processed. VNQM no longer ignores CDR files for all call managers except the last one added.

Avaya Call Manager now shows the correct numbers of phones.^*

Avaya RTCP data is collected and displayed as expected. Logs no longer include errors associated with the UTC offset.^*