Documentation forServer & Application Monitor

SAM 2020.2.1 Release Notes

Release date: August 25, 2020

These release notes describe new features, improvements, and fixed issues in SolarWinds SAM 2020.2.1. They also provide information about installation, upgrades, and workarounds for known issues.

Note the following details about this service release:

Learn more

New features and functionality

This service release includes the following changes:


New customer installation

Return to top

Use the Orion Installer, available in the Customer Portal, to install SAM. See the Orion Platform Products Installation and Upgrade Guide for details. After installation, see the SAM Getting Started Guide to learn about configuring and customizing SAM.

Before you upgrade

To prepare for the upgrade:

  1. Read these Release Notes.
  2. Confirm that all servers comply with SAM 2020.2 System Requirements.
  3. (Optional) Back up any custom code, such as modified SolarWinds .css files or added .js files. Click here for tips.

If upgrading from a previous version, be aware of the following:

SolarWinds recommends checking THWACK periodically for updates to SAM's out-of-the-box (OOTB) templates. Apart from AppInsight templates, SAM doesn't update templates automatically during upgrades to avoid overwriting custom changes you may have made. For details, see Import and export SAM templates.

Upgrade to a localized version of SAM

SAM supports localized SAM templates in German or Japanese. To switch languages when upgrading SAM, you'll need to use the Orion Installer to deploy a fresh installation of SAM and any other Orion Platform products in your environment in either language.

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 modified with custom changes. Unlike standard SAM upgrades that only update AppInsight templates, SAM 2019.4.1 replaces all templates with new versions that support localization.

  • Consult Plan your installation or upgrade for additional steps, such as:

    • Backing up your database,
    • Taking snapshots of VMs and containers, and
    • Backing up custom code, such as .css, .aspx, and .config files.
  • SolarWinds recommends testing your reinstalled version in a staging environment.

How to upgrade

Use the Orion Installer to upgrade your entire Orion deployment (all Orion Platform products and any scalability engines). See Install or upgrade Orion Platform products.

If upgrading from SAM 6.9 or later, you can upgrade your entire Orion deployment from the My Orion Deployment page (Settings > My Orion Deployment). Downloading the Orion Installer is no longer necessary.

If you need to migrate SAM as part of your upgrade, see the Orion Platform Migration Guide.


Fixed issues in SAM 2020.2.1

Return to top

Case Number Description

00565132, 00565747, 00562670, 00562670, 00571269, 00558474

Code was updated to resolve polling issues on Windows 2008 R2 servers after upgrading to SAM 2020.2. Log messages showed incorrect strong names for Microsoft.Management.Infrastructure.dll. For details, click here.

N/A

$watch.Stop code in the Exchange 2010 OWA Form Login (PowerShell) template was updated. Download the latest version from THWACK here.

00329497, 00367960, 00323248, 00490529

SSL Certificate Expiration widget displays certificates for bindings on IIS servers.

00494076

AppInsight for Active Directory "Data processing error" disappears after successful polling.

00523433

Application monitors based on HTTP and HTTPS Monitor templates return accurate URLs in web page redirects, without extra characters.

00521290

Multiple component monitors are not disabled after running Set-SwisObject in a script to disable one component monitor with a specific ID.

00521290, 00425054

The AppInsight for Active Directory template was updated so the Trusts component monitor remains enabled in the template and any application monitors based on the template.

00455465

The timeout for GetAwsInstance was extended to support connections across regions before displaying available instances when adding AWS cloud accounts.

00438950, 00376973

The Min/Max Average Statistics chart was updated to restore support for multi-statistic components, as provided in SAM 6.7 and earlier.

00421082, 00354047, 00378266

When adding a new component monitor to a template, only a single copy of the component monitor is added.

00392879

Hardware health polling for UCS devices queries for faults (faultInst) but not events (eventRecord) to prevent database deadlocks that occurred due to excessive amounts of records in some environments.

00554757, 00557392, 00556438, 00570070, 00569955

PowerShell script monitors pass user credentials to target machines after upgrading to SAM 2020.2 or later.

See also Orion Platform 2020.2.1 release notes and Orion Platform hotfix release notes.


Known issues

Return to top

Days Remaining value in SSL Certificate Expiration and IIS SSL Certificate Expiration Report widgets are not updated for AppInsight for IIS.

Issue: Polling only occurs once — when AppInsight for IIS is assigned to a node — but does not continue.

Workaround: Assign the SSL Certificate Expiration Date Monitor template to the IIS node to update the SSL date daily. Click here for details.

Component monitor scripts in the AIX template do not execute if "Inherit credentials from node" is selected.

Issue: Header issues in Perl script output prevent component monitors from inheriting credentials from nodes, so scripts fail. This may impact CPU statistic, Paging statistic/sec, Percentage of using system devices, Disk operations/sec of system devices, and Top 10 active processes metrics.

Workaround: Edit component monitors to provide credentials, or avoid using "Inherit credentials from node" option for affected component monitors. Click here for details.

Application Dependency polling fails; 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 exceptions.

Workaround: Uninstall agents from nodes, remove duplicate rows in the database, and then reinstall agents. Click here for details.

Some SAM pages and widgets are not compatible with Internet Explorer (IE) 11.

Issue: Warning messages may appear when using IE 11 with features introduced in SAM 2020.2. SolarWinds recommends using a different browser (such as Chrome, Firefox, or Microsoft Edge) for the best SAM experience.

Inconsistencies in SAM SQL tables

Issue: After upgrading to SAM 6.9 or later, a known Microsoft issue may create inconsistency in SQL tables, as indicated by a Database Integrity Check message.

Workaround: Back up the Orion database and execute a SQL query provided here.

Windows Scheduled Tasks Monitor (WSTM) polling fails for Active Directory nodes with UPN-formatted credentials.

Issue: If you add the Windows Scheduled Tasks Monitor to an Active Directory node with User Principal Name (UPN) credentials (for example, user@domain.tld, instead of domain.tld\user), polling fails, an "Access is denied" error appears in the Windows Scheduled Tasks widget, and errors appear in logs.

Workaround: Use the down-level logon name format (domain\user) instead of UPN format (user@domain). Click here for details.

High memory utilization for SolarWinds.ServiceHost.Process slows Active Directory (AD) servers monitored by Orion agents.

Issue: The ServiceDirectoryClient component leaks Service Directory client connections due to exceptions that occur when opening the channel.

Workaround: Upgrade to the latest release of SAM or switch polling method for AD servers. Click here for details.

Microsoft Windows Server 2008 R2-2012 R2 Failover Cluster (Advanced) template fails with errors and node status switches to Down.

Issue: The 64-bit FailoverClusters module conflicts with PowerShell bitness so polling fails.

Workaround: Modify a script included in the templates; click here for details.

Warranty data does not appear after Asset Inventory polling of HPE Proliant servers.

Issue: API-related changes to HP Warranty servers interrupt periodic polling. No workaround is currently available. Click here for details.

SolarWinds recommends using the Orion agent for Linux to monitor Wildfly (formerly JBoss) systems. However, note that the JMX bridge can be configured to monitor WildFly or JBoss targets, but not both types simultaneously.

Issue: WildFly, formerly known as JBoss, is an application server developed by Red Hat. For details, see Configure JMX monitoring on WildFly servers.

Application dependency polling is not supported on target Linux systems that use GNU C Library (glibc) 2.17 or earlier.

Issue: As described here, SAM deploys agent plug-ins to target systems to monitor application connections. Plug-ins deployed by SAM 2020.2 and 2020.2.1 include an Nping executable binary that doesn't support distributions based on glibc 2.17 or earlier, such as CentOS and Red Hat Enterprise Linux (RHEL) 6. As a workaround, update Linux distributions on target systems. SolarWinds recommends testing in an experimental OS first.

Applications hosted on Windows 2008 R2 servers switch to Unknown state after upgrading to SAM 2020.2.

Issue: This issue occurs if SAM cannot locate a referenced assembly in the Global Assembly Cache (GAC). Click here for workarounds.

AppInsight for Active Directory stops polling after upgrade to SAM 2020.2.

Issue: If AppInsight for Active Directory stops working and an "Unable to start polling" message appears on the AppInsight for Active Directory Details page, make sure the version of .NET Framework on target nodes matches the version on the Orion server. SAM 2020.2 uses .NET 4.8. Click here for details.

AppInsight for IIS polling on Windows 2008 servers may cause WinRMFeatureService errors in logs.

Issue: Starting in SAM 2020.2, WinRM is the default transport method to collect data for WMI-based component monitors. When monitoring Windows Server 2008 nodes with AppInsight for IIS, the following message may appear in application logs:

{{ERROR SolarWinds.APM.Probes.Management.WinRmFeatureService - Windows version 6.1.7601 with SP 1 does not support InvokeMethod }}.

The default log location is C:\ProgramData\SolarWinds\Logs\APM\ApplicationLogs.

This message appears because the WinRM Invoke method is not supported by Server 2008, but fallback should still occur and IIS servers will be polled.


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

June 4, 2020

End-of-Life (EoL) announcement – Customers on SAM 6.6 and SAM 6.7 should begin transitioning to the latest version of SAM.

September 4, 2020

End-of-Engineering (EoE) – Service releases, bug fixes, workarounds, and service packs for SAM 6.6 and SAM 6.7 will no longer be actively supported by SolarWinds.

September 3, 2021

EoL – SolarWinds will no longer provide technical support for SAM 6.6 and SAM 6.7.

July 31, 2019

EoL announcement – Customers on SAM 6.5 should begin transitioning to the latest version of SAM.

December 30, 2019

EoE – Service releases, bug fixes, workarounds, and service packs for SAM 6.5 will no longer be actively supported by SolarWinds.

June 30, 2020

EoL – SolarWinds will no longer provide technical support for SAM 6.5.

March 12, 2019

EoL announcement – Customers on SAM 6.4 should begin transitioning to the latest version of SAM.

June 12, 2019

EoE – Service releases, bug fixes, workarounds, and service packs for SAM 6.4 will no longer be actively supported by SolarWinds.

June 12, 2020

EoL – SolarWinds will no longer provide technical support for SAM 6.4.

April 6, 2018

EoL announcement – Customers on SAM 6.3 should begin transitioning to the latest version of SAM.

June 6, 2018

EoE – Service releases, bug fixes, workarounds, and service packs for SAM 6.3 will no longer be actively supported by SolarWinds.

June 6, 2019

EoL – SolarWinds will no longer provide technical support for SAM 6.3.

See Currently supported software versions for more information.


Legal notices

Return to top

© 2020 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.