SRM 2023.2 release notes
Release date: April 18, 2023
Last updated: June 13, 2023
New features and improvements in SRM: June 13, 2023
Here's what's new in SRM 2023.2. You can find the applicable system requirements here.
To view release notes, system requirements, and product guide PDFs for supported versions of SRM, see SRM previous versions. To view release notes for multiple versions
SRM runs on the SolarWinds Platform (self-hosted). SRM release notes include the updates from the SolarWinds Platform (self-hosted).
New features and improvements in SRM
Last updated: June 13, 2023
NetApp AIQUM REST API connections
SRM now supports NetApp AIQUM REST API connections.
New features and improvements in SolarWinds Platform
Security improvements
- Security improvements for external alert actions. Only users with server admin rights are able to create new external actions. See Approve alert actions executing a script.
- SMTP authentication improvements
- SSH security improvements
Additional updates
- SolarWinds Platform Agent now supports RHEL 9.0.
- Credential API now supports SAM.
- Options to disable showing contextual help, new release summaries, or notifications on new versions and security updates are added. In Advanced Configuration settings, search for SolarWinds.Guides and clear the options you want to disable. See Access the Advanced Configuration.
- New low-privilege accounts were introduced for reporting: the ReportingClient database user and the Reporting database role. See SolarWinds Platform Service Accounts.
Fixed CVEs
At SolarWinds, we prioritize the swift resolution of CVEs to ensure the security and integrity of our software. In this release, we have successfully addressed the following CVEs.
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-2022-47509 | SolarWinds Platform Incorrect Input Neutralization Vulnerability | The SolarWinds Platform was susceptible to the Incorrect Input Neutralization Vulnerability. This vulnerability allows a remote adversary with a valid SolarWinds Platform account to append URL parameters to inject HTML. | 4.3 Medium | Juampa Rodriguez (@UnD3sc0n0c1d0) |
| CVE-2022-36963 | SolarWinds Platform Command Injection Vulnerability | The SolarWinds Platform was susceptible to the Command Injection Vulnerability. This vulnerability allows a remote adversary with a valid SolarWinds Platform admin account to execute arbitrary commands. | 8.8 High | Piotr Bazydlo (@chudypb) of Trend Micro Zero Day Initiative |
| CVE-2022-47505 | SolarWinds Platform Local Privilege Escalation Vulnerability | The SolarWinds Platform was susceptible to the Local Privilege Escalation Vulnerability. This vulnerability allows a local adversary with a valid system user account to escalate local privileges. | 7.8 High | Piotr Bazydlo (@chudypb) of Trend Micro Zero Day Initiative |
| CVE-2023-23839 | SolarWinds Platform Exposure of Sensitive Information Vulnerability | The SolarWinds Platform was susceptible to the Exposure of Sensitive Information Vulnerability. This vulnerability allows users to access Orion.WebCommunityStrings SWIS schema object and obtain sensitive information. | 6.8 Medium |
Fixed customer issues
| Case number | Description | Platform product |
|---|---|---|
| 1286152, 1288976, 1289910, 1290594, 1291107, 1297401, 1307087 | The issue where date and time in custom reports did not match the format specified in Time Period was addressed. | Platform |
| 396114, 532706, 760265, 898102, 910698, 965970, 1049100, 1190709, 1199690, 1205029, 1206699, 1248892, 1257590, 1280347 | The issue where database maintenance was failing after the upgrade was addressed. | Platform |
| 1121180 | The issues with Azure Cloud Details views were addressed. | Platform |
| 1232029 | Removed SolarWinds Platform Agent plugins are marked for uninstallation after the upgrade. | Platform |
| 1289446 | The issue where SolarWinds Administration Service read and wrote the package type to an incorrect registry path was addressed. | Platform |
| 1272370, 1273749 | The issue where importing alerts with SQL macro variables was blocked for Admin users was addressed. | Platform |
| 842639 | The issue where time zones of SQL server and SolarWinds Platform polling engines showed a warning even when the zones were the same was addressed. | Platform |
| 1052957, 1240424, 1245960, 1246538, 1256606, 1257671, 1266763, 1276328, 1267382, 1279002, 1280926, 1281291, 1283928, 1288216, 1290612, 1291755, 1295777, 1296218, 1297821, 1297859 | SolarWinds Information Service performance issues when users without admin rights use PerfStack were addressed. |
Platform |
| 1270128 | The issue where the Configuration Wizard failed when configuring the website because of an applicationHost.config error was addressed. | Platform |
| 894237 | The issue where Global search could not be disabled on some pages was addressed. | Platform |
| 1278031 | The issue where users could not set up new alerts using DateTime was addressed. | Platform |
| 1229785, 1244480, 1274324 | The issue where manually created connections on Maps only showed when the Auto-Generated connection box was selected was addressed. | Platform |
| 1264223, 1279159 | The issue where scalability engines could be upgraded to the version installed on the main polling engine when upgrades for the main polling engine were available was addressed. | Platform |
| N/A | The issue where the name of sender was not specified for some out-of-the-box alerts was addressed. | Platform |
| 1125893, 1220248, 1239230, 1244512, 1249564, 1251466, 1254246, 1258643, 1258669, 1260390, 1261995, 1262474, 1264367, 1265533 | The partition management during the Database Maintenance was optimized. | Platform |
| N/A | The issue where installation/upgrade failed because of a locked file was addressed. | Platform |
| 1241480 | The issue where the send trap alert action stops working after the upgrade from 2020.2.6 was addressed. | Platform |
| 1236663, 1236783, 1241870, 1242442, 1244793, 1249353, 1251317, 1273624 | The issue when attempting to add accounts was addressed. | Platform |
| 1207061 | The installation error while running the centralized upgrade was addressed. | Platform |
| 1249722 | The issues with the "less than X objects meet the condition" condition in alerts were addressed. | Platform |
| 1245612, 1248898 | The issues with the Configuration Wizard launching automatically was addressed. | Platform |
| 1244008 | The issue where custom charts changed behavior was addressed. | Platform |
| 1229115 | The issue where AmsProxy logs stopped logging on log level change was addressed. | Platform |
| 1237514, 1243831, 1245680, 1274269, 1289216 | The issue where the node last boot was displayed using UTC was addressed. Last boot is displayed using the local time. | Platform |
| 1154578 | The issue with loading Subcategory when creating a ServiceNow incident was addressed. | Platform |
| 826160, 864527, 873077 | The issue where no error message was displayed when the upgrade failed was addressed. | Platform |
| 1239689, 1279354 | The issue where the Permission Checker fails on upgrade from 2020.2.6 for additional polling engines was addressed. | Platform |
| 1228441 | The issue where the category was not parsed correctly in All Nodes widgets was addressed. | Platform |
| 1234160, 1254686 | The issue where proportional widgets do not parse statuses was addressed. | Platform |
| 1205283 | The issue where Windows Agents generated high CPU usage was addressed. | Platform |
| 1228673 | The issue where the installation fails if there is another suspended MSI installation in the system was addressed. | Platform |
| 1214950 | The issue where latency between polling engines was incorrectly indicated on the main server was addressed. | Platform |
| 1216266 | The issue with time zones of SQL server and the main polling engine was addressed. | Platform |
| 1187919, 1209102 | The issue with Fortinet Fortigate 101E incorrectly polling IP addresses was addressed. | Platform |
| 1202271, 1246753, 1256631, 1259934, 1263843, 1282054, 1289795 | The issue where scheduled unmanaging issues caused false positive alerts was addressed. | Platform |
| 1217121, 1291663 | The issue where upgrade from 2020.2.6 fails in the Configuration Wizard when the bound HTTPS certificate is not available on the system anymore was addressed. | Platform |
| 1194008 | The issue where administrators could update the database with queries in the Add/Edit Report wizard was addressed. | Platform |
| 1186572, 1288230 | The issue where users could not save changed rows in Manage Entities was addressed. | Platform |
| 1154256 | The issue where users could not change the SNMPv3 credentials set for a node was addressed. | Platform |
| 930171, 990401, 1048906, 1054670, 1095761, 1102507, 1208626 | The issues with obsolete records in Cortex documents were addressed. | Platform |
| 1163369 | The issues with assigning a new dashboard as the default summary view were addressed. | Platform |
| 1150632 | The issue where the testing credentials for the execute external program alert action triggered the action instead of only validating the credentials was addressed. | Platform |
| 1106632 | The issues with using SQL/SWQL variables in the SMS alert action were addressed. | Platform |
| 1128730 | The issue where the Active Diagnostics test "Check Engines and OrionServers integrity" was case-sensitive was addressed. | Platform |
| 1198603, 1204150, 1226617, 1228488, 1269783, 1278674, 1279332 | The issue where the PerfStack real-time polling ignored account permissions was addressed. | Platform |
| 1088944 | The issue where volume charts behave differently for administrators and non-administrators was addressed. | Platform |
| 318702, 874297, 932513, 1076268, 1200393 | The issue where audit events for alert suppression showed time in UTC was addressed. | Platform |
| 773793, 916997, 1092088 | The issue where High Availability applications and components are not licensed was addressed. | Platform |
| 631312, 807280, 817116, 1048102, 1051103, 1133802 | The issues with latest baseline graphs were addressed. | Platform |
| 01038923 01194123 01282207 | SRM polling can once again reach the Huawei OceanStor Dorado device. | SRM |
Installation or upgrade
Use the SolarWinds Installer to upgrade your entire SolarWinds Platform deployment (all SolarWinds Platform products and any scalability engines) to the current versions.
You must be on version 2020.2.1 or later to upgrade to the current version. If you are on 2020.2 or earlier, first upgrade to 2020.2.6 and then upgrade to the current version.
Before you upgrade from 2020.2.x
-
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 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.
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 have an Orion Platform product version 2020.2 or earlier.
DPAIM
DPAIM can be installed in either of the following ways:
-
With SolarWinds SAM
DPAIM is automatically installed with SolarWinds SAM. If you have SAM, all you have to do is set up the integration module.
To install SAM, use the SolarWinds Platform Installer.
-
Standalone (SAM not required)
If you do not plan to install SAM, download and run the SolarWinds Platform Installer to install DPAIM as a separate product. You can install DPAIM alone, or you can install DPAIM with other SolarWinds Platform products, such as SolarWinds SRM.
After you install DPAIM, you must set up the DPA Integration Module.
Known issues
Last updated: November 1, 2023
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.
Polling issues caused by the JobEngine being unable to submit a job
Polling issues caused by the JobEngine being unable to a submit job for some time. In SolarWinds.JobEngineService_v2023_2.log, you will find repeated “Unable to add worker process for” warnings.
Resolution or workaround:
-
On the main polling engine, back up the
<installPath>\SWJobEngineSvc2.exe.configfile. -
Open the
SWJobEngineSvc2.exe.configfile, search for<jobSchedulerSettings_Full, and add thejobExecutionCount="10000000"parameter tojobSchedulerSettings_Fulltag. The tag should start as follows:<jobSchedulerSettings_Full jobExecutionCount="10000000"
-
Restart the JobEngine service in SolarWinds Platform Service Manager.
-
Repeat the steps on all polling engines.
Custom SQL reports stop working after the upgrade to 2023.2
Resolution or workarounds:
-
If you have issues with accessing the Flow Storage, the Log Analyzer Database, or any other database, see Custom SQL reports fail after the upgrade to 2023.2 (Error executing SQL: not able to access the database 'SolarWindsOrionLog', 'FlowStorage', or a custom database.
-
If your report requires accessing the SolarWindsOrion database, see Custom SQL reports fail after the upgrade to 2023.2 (Error executing SQL: database 'SolarWindsOrion').
Changes to the SolarWinds Platform database
The implementation of time series widgets required changes to the SolarWinds Platform database. If you have custom reports or alerts that query the database, they could be affected by these changes.
Resolution or workaround: SolarWinds recommends using API calls instead of database queries to collect data for custom reports and alerts.
Date range is one day behind on Wait Time resources
The date on Wait Time Trends resources is one day behind for environments where the DPA server and SolarWinds Platform server are in different time zones. The affected resources are:
-
All Instances with the Highest Wait Times
-
Instances with the Highest Wait Times
-
Greatest Downward Wait Time Trends
-
Greatest Upward Wait Time Trends
Resolution or workaround: Set the DPA and SolarWinds Platform servers to the same time zone.
DPAIM stops working after failover
If you have High Availability configured, the DPA Integration Module stops working when a failover occurs after you re-integrate with a previously integrated DPA server.
Resolution or workaround: Re-integrate the DPA server.
End of life
| Version | EoL announcement | EoE effective date | EoL effective date |
|---|---|---|---|
| 2020.2.6 | April 18, 2023: End-of-Life (EoL) announcement – Customers on SRM version 2020.2.6 or earlier should begin transitioning to the latest version of SRM. | May 18, 2023: End-of-Engineering (EoE) – Service releases, bug fixes, workarounds, and service packs for SRM version 2020.2.6 or earlier will no longer actively be supported by SolarWinds. | May 18, 2024: End-of-Life (EoL) – SolarWinds will no longer provide technical support for SRM version 2020.2.6. |
| 2020.2.5 | January 18, 2023: End-of-Life (EoL) announcement – Customers on SRM version 2020.2.5 or earlier should begin transitioning to the latest version of SRM. | February 17, 2023: End-of-Engineering (EoE) – Service releases, bug fixes, workarounds, and service packs for SRM version 2020.2.5 or earlier will no longer actively be supported by SolarWinds. | February 17, 2024: End-of-Life (EoL) – SolarWinds will no longer provide technical support for SRM version 2020.2.5. |
| 2020.2.4 | October 19, 2022: End-of-Life (EoL) announcement – Customers on SRM version 2020.2.4 or earlier should begin transitioning to the latest version of SRM. | November 18, 2022: End-of-Engineering (EoE) – Service releases, bug fixes, workarounds, and service packs for SRM version 2020.2.4 or earlier will no longer actively be supported by SolarWinds. | November 18, 2023: End-of-Life (EoL) – SolarWinds will no longer provide technical support for SRM version 2020.2.4. |
| 2020.2.1 | October 19, 2022: End-of-Life (EoL) announcement – Customers on SRM version 2020.2.1 or earlier should begin transitioning to the latest version of SRM. | November 18, 2022: End-of-Engineering (EoE) – Service releases, bug fixes, workarounds, and service packs for SRM version 2020.2.1 or earlier will no longer actively be supported by SolarWinds. | November 18, 2023: End-of-Life (EoL) – SolarWinds will no longer provide technical support for SRM version 2020.2.1. |
| 2020.2 | October 19, 2022: End-of-Life (EoL) announcement – Customers on SRM version 2020.2 or earlier should begin transitioning to the latest version of SRM. | November 18, 2022: End-of-Engineering (EoE) – Service releases, bug fixes, workarounds, and service packs for SRM version 2020.2 or earlier will no longer actively be supported by SolarWinds. | November 18, 2023: End-of-Life (EoL) – SolarWinds will no longer provide technical support for SRM version 2020.2. |
| 2019.4 | July 27, 2022: End-of-Life (EoL) announcement – Customers on SRM version 2019.4 or earlier should begin transitioning to the latest version of SRM. | August 26, 2022: End-of-Engineering (EoE) – Service releases, bug fixes, workarounds, and service packs for SRM version 2019.4 or earlier will no longer actively be supported by SolarWinds. | August 26, 2023: End-of-Life (EoL) – SolarWinds will no longer provide technical support for SRM version 2019.4. |
| 2019.2 | July 27, 2022: End-of-Life (EoL) announcement – Customers on SRM version 2019.2 or earlier should begin transitioning to the latest version of SRM. | August 26, 2022: End-of-Engineering (EoE) – Service releases, bug fixes, workarounds, and service packs for SRM version 2019.2 or earlier will no longer actively be supported by SolarWinds. | August 26, 2023: End-of-Life (EoL) – SolarWinds will no longer provide technical support for SRM version 2019.2. |
See the End of Life Policy for information about SolarWinds product life cycle phases. To see EoL dates for earlier SRM versions, see SRM release history.
End of support
This version of SRM no longer supports the following platforms and features.
Browser support
All versions of Internet Explorer will become unsupported in a future release. Some pages are not compatible with IE 11. Do not enable Enterprise Mode in IE 11. It is not supported.
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.
Legacy charts
Legacy charts are deprecated as of this release. Migrate your charts to their modern version.
Classic charts
Classic charts are deprecated as of this release. Migrate your charts to their modern version.
Report writer
Use the web-based Report Manager to create reports.
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.
Starting with 2024.2, you can enable the port in Advanced Configuration by clearing the DisableSwisRestEndpointOnPort17778 option. See Enable/disable the SWIS endpoint port.
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.
Starting with 2024.2, you can import Network Atlas maps to Intelligent Maps. See Import maps.
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.
SOLARWINDS DISCLAIMS ALL WARRANTIES, CONDITIONS, OR OTHER TERMS, EXPRESS OR IMPLIED, STATUTORY OR OTHERWISE, ON THE DOCUMENTATION, INCLUDING WITHOUT LIMITATION NONINFRINGEMENT, ACCURACY, COMPLETENESS, OR USEFULNESS OF ANY INFORMATION CONTAINED HEREIN. IN NO EVENT SHALL SOLARWINDS, ITS SUPPLIERS, NOR ITS LICENSORS BE LIABLE FOR ANY DAMAGES, WHETHER ARISING IN TORT, CONTRACT OR ANY OTHER LEGAL THEORY, EVEN IF SOLARWINDS HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
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.