Submit a ticketCall us
Home > Success Center > Archive > 2018June25 - InfoDev Deletes > SAM 6.1.1 Release Notes

SAM 6.1.1 Release Notes


This article is slated for Deletion. Do not update this article. If you have questions please send a message to

Created by Caroline Juszczak, last modified by Nigel on Aug 08, 2016

Views: 906 Votes: 0 Revisions: 7

Updated April 29, 2014


These release notes provide additional guidance for SolarWinds Server & Application Monitor (SAM) version 6.1.1.

Installing this Version

As with all modifications to your production environment, it is suggested that you complete the following tasks before implementing any changes:

If you need a temporary license to install an instance of the software in a lab, please download an evaluation copy of the latest software from our website. Evaluation copies come with a fully functional 30-day license.

SAM Administrator's Guide


  • Additional Orion Web Servers must be able to communicate with the primary SAM server on TCP port 17777. If you are within a secured network and have separated the polling engine component from the Web Console or are using additional pollers, make sure the polling engine is reachable on port 17777.
  • Whenever you upgrade SAM, ensure you first back up your database.

Upgrading and Configuring

Important: For customers with additional pollers, please note that the 'Local-Only' setting was removed in SAM 5.5. For more information on how this may impact your environment, see SWKB 4429.

If you have both NPM and APM installed, upgrade NPM on all SolarWinds servers first, followed by the pollers. Once that is complete, you can successfully upgrade to this release of SAM. Failure to upgrade in the correct order will result with the Configuration Wizard generating a Database Configuration Failure error.

If you have additional pollers or web consoles, upgrade them at the same time as your SolarWinds server. Update the main poller first, then the additional pollers and/or web consoles. Additional web consoles and pollers communicate with the primary SAM server on port 17777.

Follow the appropriate procedure in the section "Upgrading Server & Application Monitor" in the SolarWinds Server & Application Monitor Administrator Guide.

Repeat this procedure for any additional pollers or Web Consoles, making sure to use the correct installers for pollers (SolarWinds-Orion-APM-vx.y.z-Poller.exe) or web consoles (SolarWinds-Orion-APM-vx.y.z-WebOnly.exe), since these are different from the standard installer package.

If you are licensed for additional polling engines or additional web servers, they can be found in your SolarWinds Customer Portal. The additional Poller components must be installed on all additional pollers. The additional web server components should also be installed on all additional web servers. Both the additional poller and web server components should be at the same version as the primary SAM server.


  • If you purchase a SAM license to use with NPM, the additional nodes allowed in the SAM license can monitor CPU, Memory, and response times for nodes.
  • Downgrades of SolarWinds products are not supported. If you are upgrading or installing multiple SolarWinds products, confirm that you are installing them in the order given in the Upgrade Instructions located in your SolarWinds Customer Portal.
  • If you are not up to date on your maintenance, you will not be able to install service releases.

Migrating to Another Server

If you are installing the new SAM version to a new server, but plan to use an existing database, you are required to manually copy the original security certificate to the new server before installing the new SAM version. Otherwise you will need to re-enter passwords for all your SAM credentials. For information about copying the security certificate and a workaround to avoid re-entering passwords (if you migrated without copying the security certificate), refer to the following knowledge base article: How can I migrate my credentials when upgrading Orion APM 3.5 to Orion APM 4.0, or higher, on a new server?

Open Issues in this Release

This release of SolarWinds SAM includes the following open issues:

  • There are no open issues in this release.

Fixed Issues and Additions in this Release

This release of SAM includes the following fixes and additions:

Version 6.1.1

Fixed Issues:

  • An issue where certain Asset Inventory resources were displaying volumes that were not appearing in the web console has been fixed. a
  • The Exchange database file size default limit was increased in size from 50 GB to 1 TB, and can now be configured manually in the following file: SolarWinds.APM.BlackBox.Exchg.Collector.dll.config.  The 50 GB limit made it difficult to determine proper thresholds. b
  • An issue where AppInsight for Exchange incorrectly calculated the limit for any mailbox database on Exchange 2010 Standard Edition at 50GB has been resolved. c
  • An issue where a PowerShell scripts are unable to run because user accounts and the Exchange server are from different domains has been resolved. d
  • An issue where AppInsight for Exchange threw an error citing, Exchange Version Mismatch, has been resolved. e
  • A conflict between:
    • Windows Scheduled Task Manager and templates of the same name causing the former not to function properly, has been fixed. f
    • AppInsight applications and templates of the same name causing the former not to function properly, has been fixed.  m
  • An issue where certain Asset Inventory resources were showing duplicate records due to external updates  has been fixed. g
  • AppInsight for Exchange now has the ability to poll all mailboxes within a domain forest. Prior to this fix, AppInsight for Exchange could only poll root mailboxes.
  • A memory leak has been fixed. This leak occurred during the attempted initialization of certain performance counters resulting in performance counters endlessly attempting to start. i
  • An issue where some physical servers being monitored were falsely reporting a child Warning status has been fixed. j
  • AppInsight for Exchange now supports Windows 2008 (non-R2). k
  • A timeout setting has been increased for Linux script execution which now prevents a script execution error. l
  • A Linux script execution error has been fixed. n, p, q
  • After  upgrading to SAM 6.1, an issue where the variables, ${Threshold-Statistic-Critical} and ${Threshold-Statistic-Warning}no longer populated, has been fixed. o

Table of Fixed SAM Issues

The following table provides the internal Development ID numbers and external support ID numbers for fixed SAM issues as well as new feature requests in this release. Search in the support ID number column for the number assigned to your support case.

Superscript Support ID number Development ID number
a 591714 321074
b 586749 318056
c 603164 328359
d 591412 320755
e 593737 321838
f, m 594985, 602168 323456, 328549
g 576182 312166
h 581448 314906
i 490700 255402
j 577567 312188
k 596422 324735
l 599218 326004
n, p, q 594888, 583631, 601187 323753, 325219, 327131
o 598659 325679


Last modified