Documentation forSolarWinds Platform

SolarWinds Platform 2023.4 release notes

Release date: November 1, 2023

Here's what's new in SolarWinds Platform 2023.4.

Learn more

New features and improvements in SolarWinds Platform

  • SD-WAN monitoring was improved to include tunnel metrics for supported SD-WAN vendors, such as Meraki, Viptela, and VeloCloud.
  • Stability and performance improvements for SolarWinds Platform Agents.
  • Improved FIPS support
  • Anomaly-Based alerting added for virtual machines, as well as a visual representation of the normal operating range.
  • AlertStack improvements - creating SolarWinds ServiceDesk incidents from an alert cluster.
  • API Poller: The metric column data type was changed from nvarchar to float to ensure that the column does not accept any string values.
  • Intelligent Maps improvements:
    • Users can edit public maps created by other users.
    • Users can change map ownership.
    • Users can display maps based on GroupName variables.
    • Users display the list of maps for individual nodes.
    • Users can search for maps that include a specific node.
    • Map name requirements changed: map names can consist of 2 or more characters.
    • New Maps Widget added.

Return to top


Case number Description
01267155, 01421126, 01438926, 01443423

The Job Engine no longer sends unnecessary messages to Linux Agents. The load generated by these messages could cause packet loss and connection issues.

01221457, 01293288, 01354612, 01395445, 01427582, 01430113

In environments with High Availability pools, the SolarWinds Agent configuration was improved so that the Agents do not experience connection issues or do not connect to an incorrect polling engine. The issues were caused by incorrectly assigned engine IP addresses.


The SWQL query for unpaid HCO or module nodes has been optimized to prevent it from timing out in certain environments. The query now runs successfully and returns the correct number of licensed nodes.

01354525, 01372311, 01427582

AgentManagement message processing has been improved. This change fixes an issue that caused packet loss and high response times for agents, with messages such as Messaging.IncomingMessageProcessor - Unable to deliver response message.


When you select Root Level Groups as the view mode on the Manage Groups page, the pagination and the number of rows is correct.


When you run database maintenance manually, the swdebugMaintenanceExecutionHistory.log shows the time the job started as well as the time it completed.


On a computer with a Thai calendar, the configuration wizard no longer fails during an upgrade with the following messages:

Error running task Orion.MessageBus.MessageBusConfigurator Configuring message bus

SolarWinds.ConfigurationWizard.Common.ConfigurationException: Failed to setup RabbitMQ for Orion.

01245960, 01257671, 01332739, 01337918, 01379927, 01405546

Opening a page containing PerfStack charts no longer causes the SolarWinds Platform to become unresponsive due to increased CPU and memory usage. In addition, the performance of PerfStack charts has been improved.

00323316, 01155264, 01396839

The macro ${N=Alerting;M=Notes} works correctly. When an alert definition includes that value, the associated information is included in the alert notification.


A condition that caused an extremely large number of alerts to be generated in some environments has been fixed.

01375520, 01407345, 01415367

SSH connections to a node from an additional web server no longer fail if a firewall is configured to restrict outbound connections to the node on port 22.

01245979, 01313243, 01407384

The SolarWinds Platform no longer fails periodically with errors like the following:

  • There was an error retrieving data from SolarWinds Information Service

  • Cannot access a disposed object. Object name: 'System.ServiceModel.Channels.ServiceChannel'.


If you have multiple alerts with the same condition, all of those alerts are triggered and reset as expected.


It is possible to add a node with more than 15,000 interfaces.


The SolarWinds Platform notifies you of failed login attempts in case an unknown user or a user with an invalid password is attempting to access the system. Invalid notifications are no longer sent when the login succeeds but the credentials were not in the default format.


To improve the performance of the Active Alerts view in the SolarWinds Web Console, alert history will be deleted from the SolarWinds Platform database after the specified retention period. By default, the retention period is 90 days. To change the default value:

  1. Click Settings > All Settings.

  2. Under Thresholds & Polling, click Polling Settings.

  3. Change the value of the Alerts History Retention setting.


If your system is set to a language that uses commas to represent decimals, and you have custom properties that are floating point numbers with predefined values, it is now possible to enter or select values for these custom properties.

01354791, 01354869, 01355410, 01362922, 01375906, 01373611, 01382105

For security reasons, SolarWinds Platform 2023.2 added the dedicated database user ReportingClient with the Reporting role. This user queried the SolarWinds Platform database to gather report data. The user was granted only the privileges needed to perform that task. This user could not query other, custom databases; therefore, any reports, widgets, or queries to custom database stopped working.

To resolve this issue, use the Database Manager or the Server Management Studio to edit the WebSettings table in the SolarWinds Platform database. Change the value of ReportingSQLReportsUseDBServerLevelLogin to true.

When ReportingSQLReportsUseDBServerLevelLogin is set to true, the database account that was specified in the Configuration Wizard is used to query the database. By default, this is SolarWindsOrionDatabaseUser.


Request filtering rules that deny access to files with certain extensions can prevent the SolarWinds Platform installer and Web Console from functioning correctly. To prevent this issue, the Configuration Wizard now implements request filtering rules that explicitly allow access to the required file extensions.


To prevent timeouts when the passive agent protocol is sending data from the agent to AMS, throughput between the passive agent and the SolarWinds Platform server was improved by optimizing the transfer block size.


When multiple nodes have the same IP addresses, Network Discovery no longer adds interfaces to the wrong node.


The JobEngine agent correctly purges .result files.

01200338, 01263383, 01302935, 01305295, 01307270, 01354496, 01355266, 01373795, 01374238, 01379084, 01381609, 01383437

This release fixes an issue that was preventing Network Atlas maps from opening or affecting performance for maps that did open.

00402725, 00550290, 01313151

In previous versions, HA tables needed to be truncated before a migration. If they weren't, a Centralized Upgrade would fail with the error System.Data.SqlClient.SqlException.

In 2023.4 and later, you no longer need to truncate HA tables before a migration, and duplicate rows in these tables no longer halt a Centralized Upgrade.

01292325, 01307456

The Polling Engines page no longer lists the same additional polling engine multiple times in some circumstances.

00453177, 00480501, 01210125

The Unmanage Task Editor no longer adds an error message in the logs even though the task completed successfully.

01310143, 01372569

The SolarWinds Installer no longer stops with the message that the Windows Event Log, Network List Service, and Network Location awareness applications must be closed for the installation to continue.


An attribute that could cause a memory leak has been removed from the SolarWinds Job Engine.

01174799, 01366508, 01308406, 01384094, 01397934, 01400006, 01416989

Alerts with an automatic reset condition no longer stop resetting after certain events, such as the database being temporarily disconnected.

00059548, 00666436, 00764976, 01159109

Top XX Capacity widgets can be filtered using custom properties.


NFSv2 and NFSv3 network disks for AIX systems are now correctly classified as network disks instead of fixed disks.

01267155, 01328071

A situation that could cause the Linux Job Engine to run a job outside its scheduled interval has been corrected.


The Job Engine no longer causes DNS lookups to fail.


If ServiceNow has an Authentication profile configuration, requests from the SolarWinds Platform to ServiceNow no longer fail with a 401 status code.*

01439374, 01468220

Volume polling no longer stops due to deadlocks occurring in the CoreThreshold table.*


The throughput of the Job Engine service responsible for device polling was improved to fix issues related to polling completion below 100%, missed polls, or delayed polls.*


The Configuration Wizard no longer fails when an empty database is selected.*


When live updates are disabled for maps, information on the map viewer page is updated at the specified refresh interval.*

*This fix was added after the RC release.

SolarWinds CVEs

SolarWinds would like to thank our Security Researchers below for reporting on the issue in a responsible manner and working with our security, product, and engineering teams to fix the vulnerability.

CVE-ID Vulnerability Title Description Severity Credit
CVE-2023-40062 SolarWinds Platform Incomplete List of Disallowed Inputs Remote Code Execution Vulnerability The SolarWinds Platform was susceptible to a Remote Code Execution Vulnerability by a low privileged user. 8.0 High Piotr Bazydlo (@chudypb) of Trend Micro Zero Day Initiative
CVE-2023-40061 SolarWinds Platform Insecure Job Execution Mechanism Vulnerability Insecure job execution mechanism vulnerability. This vulnerability can lead to other attacks as a result. 7.1 High Jakub Brzozowski "redfr0g" (STM Cyber), Kamil Falkiewicz (STM Cyber), Szymon Jacek (STM Cyber)

Return to top

Before you upgrade!

If you are upgrading from 2020.2.6 or earlier, please be aware of the following:

  • Before upgrading from Orion Platform 2020.2.6 and earlier to SolarWinds Platform 2022.3 or later, make sure the database user you use to connect to your SQL Server has the db create privilege. Without this privilege, the upgrade will not complete.

  • The legacy syslog and traps functionality has been retired and replaced with a new functionality called SolarWinds Log Viewer, which can be upgraded to Log Analyzer for additional capabilities. Current rules and history will automatically be migrated to the new logging functionality (SolarWinds Log Viewer or Log Analyzer). The functionality of SolarWinds Log Viewer and Log Analyzer has been improved to more closely match legacy functionality. See LA 2022.3 release notes for details.

    If you built syslog and trap alerts using custom SQL queries, they will not function after upgrading to 2022.3 or later. SolarWinds recommends you rewrite the alerts using SWQL (Orion.OLM entities) or using the alerting functionality built into Log Viewer/Log Analyzer.

  • Some upgrade situations from the Orion Platform to the SolarWinds Platform are not supported and the installer will stop the upgrade automatically.
    • If you have a SQL Server older than 2016.
    • If you are on an Orion Platform product version earlier than 2020.2.1.

Return to top

Installation or upgrade

For new installations, you can download the installation file from the product page on or from the Customer Portal.

For upgrades, go to Settings > My Deployment to initiate the upgrade. The SolarWinds Installer upgrades your entire deployment (all SolarWinds Platform products and any scalability engines).

For more information, see the SolarWinds Platform Product Installation and Upgrade Guide.

If you are on a version earlier than SolarWinds Platform 2020.2.6, first upgrade to 2020.2.6 and then upgrade to 2023.4. Before upgrading, see Considerations for upgrading from the Orion Platform to the SolarWinds Platform.

Return to top

Known issues

Windows Agents stop polling CPU, memory, and disks after the upgrade

If you use Windows Agents with disabled automatic update of Agents and upgrade your deployment to 2023.4 or later, Agents stop polling CPU, memory, and disks.

Resolution or workaround: Update Windows Agents manually, or enable the auto-update. See Update Agents. This issue will be addressed in a future SolarWinds Platform version.

Database configuration fails during an upgrade

When you attempt to upgrade from Orion Platform 2020.2.1 through 2020.2.5 to SolarWinds Platform 2023.4 or 2023.4.1, database configuration fails. The Configuration Wizard displays the following message:

Database configuration failed: Error while executing script- Invalid column name 'AllowOrionMapsManagement'.

Resolution or Workaround: For instructions to resolve this issue, see Database configuration fails during an upgrade to SolarWinds Platform 2023.4 or 2023.4.1.

Database login fails for Windows accounts after the upgrade

When you use Windows authentication to connect to the HCO database and the database SQL server, you can find Database: Login failed for user 'DOMAIN\MACHINENAME$' in the Website log. This can cause intermittent user logouts from the SolarWinds Web Console.

Resolution or Workaround: Change the database account. See Database login failing for Windows account users after upgrading to 2023.1 and above.

Configuration wizard fails on migrating APIPoller_ValueToMonitor table

If you inserted string data in the database for the metric column of the API Poller table before upgrading to 2023.4, data migration for the APIPoller_ValueToMonitor table will fail. As a consequence, the Configuration wizard fails during the upgrade, too.

Resolution or Workaround: Complete the steps to change the data type:

  1. Verify how many records for the metric column are not numeric. Run the following query:

    SELECT  * from APIPoller_ValueToMonitor Where ISNUMERIC(Metric) <> 1
  2. For the records you identified, update the metric column to null. Run the following query:

    UPDATE APIPoller_ValueToMonitor SET Metric = NULL Where ISNUMERIC(Metric) <> 1
  3. Rerun the first step. It should return no records.

  4. Continue or re-run the Configuration Wizard.

Return to top

End of life

SolarWinds recommends you upgrade to the latest version of your products at your earliest convenience.

Version EOL Announcements EOE Effective Dates EOL Effective Dates
2022.2 November 1, 2023: End-of-Life (EoL) announcement – Customers on SolarWinds Platform 2022.2 should begin transitioning to the latest version of SolarWinds Platform. December 1, 2023: End-of-Engineering (EoE) – Service releases, bug fixes, workarounds, and service packs for SolarWinds Platform 2022.2 will no longer be actively supported by SolarWinds. December 1, 2024: End-of-Life (EoL) – SolarWinds will no longer provide technical support for SolarWinds Platform 2022.2.
2020.2.6 April 18, 2023: End-of-Life (EoL) announcement – Customers on Orion Platform 2020.2.6 should begin transitioning to the latest version of SolarWinds Platform. May 18, 2023: End-of-Engineering (EoE) – Service releases, bug fixes, workarounds, and service packs for Orion Platform 2020.2.6 will no longer be actively supported by SolarWinds. May 18, 2024: End-of-Life (EoL) – SolarWinds will no longer provide technical support for Orion Platform 2020.2.6.
2020.2.5 January 18, 2023: End-of-Life (EoL) announcement – Customers on Orion Platform 2020.2.5 should begin transitioning to the latest version of SolarWinds Platform. February 17, 2023: End-of-Engineering (EoE) – Service releases, bug fixes, workarounds, and service packs for Orion Platform 2020.2.5 will no longer be actively supported by SolarWinds. February 17, 2024: End-of-Life (EoL) – SolarWinds will no longer provide technical support for Orion Platform 2020.2.5.
2020.2.4 October 19, 2022: End-of-Life (EoL) announcement – Customers on Orion Platform 2020.2.4 should begin transitioning to the latest version of SolarWinds Platform. November 18, 2022: End-of-Engineering (EoE) – Service releases, bug fixes, workarounds, and service packs for Orion Platform 2020.2.4 will no longer be actively supported by SolarWinds. November 18, 2023: End-of-Life (EoL) – SolarWinds will no longer provide technical support for Orion Platform 2020.2.4.
2020.2.1 October 19, 2022: End-of-Life (EoL) announcement – Customers on Orion Platform 2020.2.1 should begin transitioning to the latest version of SolarWinds Platform. November 18, 2022: End-of-Engineering (EoE) – Service releases, bug fixes, workarounds, and service packs for Orion Platform 2020.2.1 will no longer be actively supported by SolarWinds. November 18, 2023: End-of-Life (EoL) – SolarWinds will no longer provide technical support for Orion Platform 2020.2.1.
2020.2 October 19, 2022: End-of-Life (EoL) announcement – Customers on Orion Platform 2020.2 should begin transitioning to the latest version of SolarWinds Platform. November 18, 2022: End-of-Engineering (EoE) – Service releases, bug fixes, workarounds, and service packs for Orion Platform 2020.2 will no longer be actively supported by SolarWinds. November 18, 2023: End-of-Life (EoL) – SolarWinds will no longer provide technical support for Orion Platform 2020.2.

See the End of Life Policy for information about SolarWinds product life cycle phases. To see EoL dates for earlier SolarWinds Platform versions, see SolarWinds Platform release history.

Return to top

Deprecation notice

The following platforms and features are still supported in the current release. However, they will be unsupported in a future release. Plan on upgrading deprecated platforms, and avoid using deprecated features.

Type Details
Network Atlas

Network Atlas is deprecated as of Orion Platform 2020.2. It is still available and supported in the current release, but will be removed in a future release. Deprecation is an indication that you should avoid expanded use of this feature and formulate a plan to discontinue using the feature. SolarWinds recommends that you start using Intelligent Maps in the SolarWinds Platform Web Console to display maps of physical and logical relationships between entities monitored by the SolarWinds Platform products you have installed.

Port 17778

SWIS REST Endpoint on port 17778 is deprecated as of 2023.1 and will be replaced with port 17774 in a future release. SolarWinds recommends that you start migrating SWIS REST Endpoint to port 17774.

If you are using DPAIM, make sure you are running DPA 2024.2 or later to switch to port 17774. Earlier DPA versions cannot send data to DPAIM on port 17774. See Specify the port DPA uses... for more information.

Return to top

SolarWinds Platform products release notes

Hybrid Cloud Observability (all versions)

Network Management

Systems Management

Legal notices

© 2023 SolarWinds Worldwide, LLC. All rights reserved.

This document may not be reproduced by any means nor modified, decompiled, disassembled, published or distributed, in whole or in part, or translated to any electronic medium or other means without the prior written consent of SolarWinds. All right, title, and interest in and to the software, services, and documentation are and shall remain the exclusive property of SolarWinds, its affiliates, and/or its respective licensors.


The SolarWinds, SolarWinds & Design, Orion, and THWACK trademarks are the exclusive property of SolarWinds Worldwide, LLC or its affiliates, are registered with the U.S. Patent and Trademark Office, and may be registered or pending registration in other countries. All other SolarWinds trademarks, service marks, and logos may be common law marks or are registered or pending registration. All other trademarks mentioned herein are used for identification purposes only and are trademarks of (and may be registered trademarks) of their respective companies.