Release Date: December 18, 2019
Updated April 20, 2020
These release notes describe new functionality and fixed issues in SolarWinds Server & Application Monitor (SAM) 2019.4.1, a service release. They also provide information about installation, upgrades, and workarounds for known issues. For release notes from earlier SAM releases, see Previous Version documentation.
Note the following details about this release:
- System requirements have not changed since the last release. Use the SAM 2019.4 System Requirements.
- SAM 2019.4.1 consumes Orion Platform 2019.4 and already includes Orion Platform hotfixes released on or before December 18, 2019.
Orion Platform products now support both perpetual licenses and subscription licenses. See License types in the Orion Platform documentation for details.
This service release introduces SAM application monitor templates in German and Japanese that are automatically available when you select one of those languages when running the Orion Installer to deploy SAM in your environment. Recommendations for installing SAM 2019.4.1 vary for new and existing customers, as described below.
For optimal results, all Orion Web Console users should modify local language settings in the Microsoft Windows operating system and web browsers. To access the latest localized documentation, click here.
To learn more about installation, review the Orion Platform Products Installation and Upgrade Guide. After installation, see the SAM Getting Started Guide to learn about configuring and customizing SAM.
To upgrade to SAM 2019.4.1 in German or Japanese, you'll need to use the Orion Installer to deploy a fresh installation of the Orion Platform in German or Japanese that includes updated, localized SAM templates. Note these important details before proceeding:
- You cannot roll back to English after installing the Orion Platform in another language.
Back up any SAM templates and application monitors with custom changes. Unlike standard SAM upgrades that only update AppInsight templates, SAM 2019.4.1 replaces all templates with the new versions that support localization.
Consult the checklist at Prepare to install or upgrade Orion Platform products for additional steps, such as:
- Backing up your database,
- Taking snapshots of your VMs and containers, and
- Backing up custom code, such as .css, .aspx, and .config files.
- SolarWinds recommends testing your reinstalled version of SAM in a test or staging environment.
Additional details about switching to SAM 2019.4.1 from another SAM version include:
- Depending on options selected in the Orion Installer, the Orion Log Viewer replaces legacy Syslog and Traps with an instant evaluation of SolarWinds Log Analyzer (LA).
- To collect trust data for AppInsight for Active Directory, configure domain controllers as GC servers that use the default port, 3268. If your domain controllers use port 3269, update that setting in your AppInsight for Active Directory template.
- The Application Dependencies feature is initially disabled to prevent performance issues for environments with large quantities of nodes. To restart polling after an upgrade, enable the Application Dependencies feature.
- If you exceed recommended cloud monitoring limits, you may receive a 503 Service Unavailable error when adding Azure accounts. Click here for a workaround.
- If using the container monitoring feature, rebuild containers and then add container services back into the Orion Platform. Click here for details.
The ADMProbe was updated so Application Dependency agent plug-in deployment succeeds on 64-bit Linux systems during upgrades.
AppInsight for Active Directory applications appear Down after disabling the Total Counters feature.
Issue: Replication polling requires a DNS or SysName value to compute replication for a destination domain controller FQDN name, but nodes configured for ICMP polling do not provide this data. As a result, AppInsight for Active Directory widgets may not reflect the actual status of ICMP nodes. Another impact is that replication widgets display IP addresses for ICMP nodes instead of assigned node names.
Workaround: Configure AppInsight for Active Directory nodes as Windows Servers that support both WMI and ICMP polling so that AppInsight for Active Directory widgets can display node status and names properly via WMI. Alternatively, edit the name of an ICMP node on the Node Details > Edit Properties page.
Application pools and websites on nodes monitored by AppInsight for IIS show Unknown status after being unmanaged.
Issue: After assigning AppInsight for IIS to a node, the application pools and websites exhibiting problem behavior could not be unmanaged in SAM. The status changed to Unknown but should appear as Down.
Workaround: Update the record in the Orion database. Click here for a workaround.
SSL Certificate Expiration widget doesn't show certificates for all bindings on IIS servers.
Issue: When AppInsight for IIS monitors a server that has two HTTPS site bindings with the same IP address and port, but different host names and SSL certificates, only the default certificate appears in the SSL Certificate Expiration widget.
Container monitoring stops after upgrade from SAM 6.7 or later.
Issue: YAML files need to be refreshed after the upgrade.
Workaround: Rebuild containers. Click here for details.
Days Remaining value in SSL Certificate Expiration and IIS SSL Certificate Expiration Report widgets not updated by AppInsight for IIS.
Issue: Polling only occurs once — when AppInsight for IIS is assigned to a node — but does not continue.
Component monitor scripts in the AIX template do not execute if "Inherit credentials from node" is selected. This issue can impact CPU statistic, Paging statistic/sec, Percentage of using system devices, Disk operations/sec of system devices, and Top 10 active processes.
Issue: Header issues in Perl script output prevent component monitors from inheriting credentials from nodes, so scripts fail.
Workaround: Either edit component monitors to provide credentials, or avoid using "Inherit credentials from node" for affected component monitors. Click here for details.
AppInsight for Active Directory performance counters appear as Unknown and may fail during SAM polling.
Issue: AppInsight for Active Directory looks for performance counters in the NT Directory Services (NTDS) category but some domain controllers store performance counters in the Directory Services category, a known Windows issue
Workaround: Rebuild Windows NTDS performance counters. Click here for details.
Application Dependency polling fails; application dependencies or connections between nodes for Windows Server and other applications do not appear as expected.
Issue: Rows in the dbo.AgentManagement_Agents table that share the same Node ID may cause an exception.
Workaround: Uninstall agents from nodes, remove duplicate rows in the database, and then reinstall agents. Click here for details.
The PowerShell version of the Server Clock Drift template returns invalid results and the following message: "Scripting Error: Script does not contain the expected parameters or is improperly formatted. 'Statistic' missing."
Issue: This may occur if the clock drift is small negative number, such as -0.001.
Workaround: This issue was fixed in SAM 6.4. If you started with a fresh install of SAM 6.4 or later, you should already have the updated template. If you began using an earlier version of SAM, download the latest version from THWACK. You can also update the code in existing templates. Click here for details.
SQL Server locking causes the Orion database to grow after assigning the AppInsight for Active Directory template to nodes in SAM
Issue: SQL Server locks may occur if you exceed recommended limits for AppInsight for Active Directory monitoring; see Best practices for AppInsight for Active Directory. Locks can prevent rows from being deleted during daily database maintenance jobs, so the number of rows grows as polling continues.
Workaround: Delete rows from the database manually, or remove AppInsight for Active Directory from nodes, wait for daily database maintenance to finish, and then add AppInsight back to the nodes. Click here for details.
The Apache template for Linux shows as Down on RedHat-derived system, such as CentOS.
Issue: The apache2 process monitor tests if a specific process — apache2 —is running, and reports the CPU and physical memory used by the process. The Apache process name may vary across Linux distributions.
Workaround: Edit the template and modify apache2 references, as necessary.
In the Microsoft Azure App Service template, the Average response time component monitor that provides the average time taken for the app to serve requests is not working.
Workaround: Disable the component. This issue will be resolved in a future release.
End of life
See the End of Life Policy for details about life cycles for SolarWinds products.
|EoL Announcements||EoE Effective Dates||EoL Effective Dates|
July 31, 2019
End-of-Life (EoL) announcement – Customers on SAM 6.5 should begin transitioning to the latest version of SAM.
December 30, 2019
End-of-Engineering (EoE) – Service releases, bug fixes, workarounds, and service packs for SAM 6.5 will no longer be actively supported by SolarWinds.
June 30, 2020
End-of-Life (EoL) – SolarWinds will no longer provide technical support for SAM 6.5.
March 12, 2019
End-of-Life (EoL) announcement – Customers on SAM 6.4 should begin transitioning to the latest version of SAM.
June 12, 2019
End-of-Engineering (EoE) – Service releases, bug fixes, workarounds, and service packs for SAM 6.4 will no longer be actively supported by SolarWinds.
June 12, 2020
End-of-Life (EoL) – SolarWinds will no longer provide technical support for SAM 6.4.
April 6, 2018
End-of-Life (EoL) announcement – Customers on SAM 6.3 should begin transitioning to the latest version of SAM.
June 6, 2018
End-of-Engineering (EoE) – Service releases, bug fixes, workarounds, and service packs for SAM 6.3 will no longer be actively supported by SolarWinds.
June 6, 2019
End-of-Life (EoL) – SolarWinds will no longer provide technical support for SAM 6.3.
See Currently supported software versions for more information.
© 2019 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.