Documentation forHybrid Cloud Observability Essentialsand Server & Application Monitor

SAM 2020.2.1 Release Notes

Release date: August 25, 2020

Updated February 10, 2021

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, note the following details:

  • The Orion Log Viewer (OLV) replaces the legacy Syslog and Trap Viewers.
  • To collect trust data for Global Catalog (GC) servers, AppInsight for Active Directory uses port 3268. If a GC domain controller uses port 3269 instead, update that setting in the application monitor assigned to the node. See Configure AppInsight for Active Directory on nodes.
  • The Application Dependencies feature is disabled during upgrades to avoid performance issues in large environments. After upgrading, enable it to restart polling.
  • If you exceed recommended cloud monitoring limits and receive a 503 Service Unavailable error when adding Azure accounts, click here for a workaround.
  • To monitor Exchange Server 2016 and later, install PowerShell 5.1 or later and provide local Administrator rights. See Using PowerShell in SAM.
  • If monitoring containers in your SAM environment:
    • Rebuild containers after upgrading and then add them back. Click here for details.
    • The Kubernetes script included in the Orion Platform was updated for Kubernetes v1.16. If you need a script designed for an earlier Kubernetes version, see this Success Center article.
  • If you upgrade to a localized version of SAM, all templates with new versions that support localization will be replaced. Back up any SAM templates and application monitors modified with custom changes. You cannot roll back to English after installing the Orion Platform in another language.
  • Due to end-of-support by Microsoft for Basic Authentication connections to Exchange Online APIs, the following templates are not included in fresh installations of SAM. Consider using API poller templates designed for Microsoft 365 instead, as described in the SAM API Poller Template Guide.

    • Microsoft Office 365 Exchange Online
    • Microsoft Office 365 Mobile Device Management
    • Microsoft Office 365 Portal
    • Microsoft Office 365 Subscription
  • The following Citrix templates are not longer included in SAM, but remain available in THWACK. Click here for the latest templates, including the Citrix Hypervisor template that replaces the Citrix XenServer template.
    • Citrix PVS Accelerator for XenServer
    • Citrix XenApp 5.0 Core WMI Counters
    • Citrix XenApp 5.0 ICA Session WMI Counters
    • Citrix XenApp 5.0 Presentation Server WMI Counters
    • Citrix XenApp 5.0 Services
    • Citrix XenServer
  • The following templates are no longer included in SAM, but remain available in THWACK. Use AppInsight for SQL to monitor the NTA Flow Storage Database instead.
    • SolarWinds NetFlow Traffic Analyzer Database
    • SolarWinds NetFlow Traffic Analyzer
  • The Orion Server 2017.3 and SolarWinds Failover Engine templates were replaced by Orion Server 2020.2 templates. Deprecated templates remain in THWACK and legacy SAM 2017.3 — 2019.4 installations.

SolarWinds recommends checking THWACK periodically for updates to SAM application monitor templates. Apart from AppInsight templates, SAM doesn't update templates automatically during upgrades to avoid overwriting custom changes. For details, see Import and export SAM application monitor templates.

How to upgrade

Starting with SAM 6.9, you can upgrade SAM directly from the Orion Web Console (Settings > My Orion Deployment). Downloading the Orion Installer is no longer necessary.

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.


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

00329497, 00367960, 00323248, 00490529

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


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


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


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.


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.


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.

The following issues were fixed in SAM 2020.2.1 Hotfix 1, released on October 29, 2020. The SolarWinds Orion Installer used to install SAM 2020.2.1 already includes this hotfix and Orion Platform 2020.2.1 Hotfix 1.

Case Number Description


WinRM fallback methods were updated so AppInsight for IIS polling detects IIS versions on web servers after upgrading to SAM 2020.2.1.

00619573, 00620940

When Orion services restart, the ApiPoller.Service starts so users can display and manage existing API pollers.


When migrating SAM to a different server, the Configuration wizard runs without errors related to database mirroring and SQL Server Availability Groups (AGs).

00605044, 00611404, 00620882, 00626409, 00627900, 00633039

For nodes that host API pollers, non-Admin users can access Node Details pages without being prompted for Windows credentials or getting authentication-related server errors. This issue may occur after upgrading to SAM 2020.2.1 if any custom properties limit access to certain nodes.


API poller authentication functionality was updated to resolve errors in API Poller Services logs in the SolarWinds\Logs\SolarWinds.Orion.ApiPoller folder, such as: Error on sql connection authorization.Selected authorization strategy:. System.InvalidOperationException: Sequence contains more than one matching element at System.Linq.ThrowHelper.ThrowMoreThanOneMatchException()


Changes to descriptions, user notes, and thresholds in AppInsight for Active Directory component monitors persist without SQL errors for the APM Business layer similar to: ERROR SolarWinds.APM.Common.MessageUtilities - Exception caught in method UpdateApplicationEx System.Data.SqlClient.SqlException (0x80131904): Cannot insert the value NULL into column 'Value', table '@componentSettings'; column does not allow nulls. INSERT fails. The statement has been terminated.

00565132, 00565747, 00562670, 00571269

SAM-12002, CUST-68343, CUST-68411, CUST-68512, CUST-68513, CUST-68734

Applications hosted on Windows 2008 R2 servers reflect correct status after upgrading to SAM 2020.2.

00554650, 00564802, 00632032, 00588438, 00602838

After upgrading to SAM 2020.2 or later, AppInsight polling succeeds without agent plugin mismatch errors similar to: [STP SmartThreadPool Thread #0] [A(null)] [C(null)] ERROR SolarWinds.APM.Probes.ApplicationJobBase - [x2] Application failed for with error of "Error converting value "ForEachOutputRowInParallel" to type 'SolarWinds.APM.Probes.ProbeResults.ChildProbesExecutionMode'.

See also Orion Platform 2020.2.1 release notes and SAM hotfixes.

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 plugins to target systems to monitor application connections. Application dependency-related plugins 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.

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 Server 2008 nodes 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 Windows Server 2008, but fallback should still occur and IIS servers will be polled.

AppInsight for IIS polling on Windows Server 2008 R2 SP1 nodes fails and applications switch to Unknown state.

Issue: Windows Server .NET 4.8 agents expect a later version of PowerShell, resulting SolarWinds.APM.Probes.CustomWmiProbe- and Microsoft.Management.Infrastructure-related errors in logfiles.

Workaround: Install PowerShell 3.0 or later on target servers. Click here for details.

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.

See Currently supported software versions for more information.

Legal notices

Return to top

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