Submit a ticketCall us

Solarwinds & Cisco Live! Barcelona
Join us from the 29th of January to the 2nd of February at Cisco Live 2018 in Barcelona, where we will continue to show how monitoring the network with SolarWinds will keep you ahead of the game. At our booth (WEP 1A), we will demonstrate how SolarWinds network solutions can help. As a bonus, we are also hosting a pre-event webinar - Blame the Network, Hybrid IT Edition with our SolarWinds Head Geek™, Patrick Hubbard on January 24th - GMT (UTC+0): 10:00 a.m. to 11:00 a.m. There's still time to RSVP.

Home > Success Center > Server & Application Monitor (SAM) > SAM 6.0 Release Notes

SAM 6.0 Release Notes

Created by Caroline Juszczak, last modified by MindTouch on Jun 23, 2016

Views: 726 Votes: 0 Revisions: 4


Updated 9/12/2013

Beginning with version 5.0, Orion Application Performance Monitor, (APM), has been renamed to SolarWinds Server & Application Monitor, (SAM). These release notes provide additional guidance for SolarWinds Server & Application Monitor (SAM) version 6.0.

Installing this Version

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

  • Back up your database.
  • Test the change in a lab environment that mimics your production environment.

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 has been removed. 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 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.

If you have version 3.1 or lower of Application Performance Monitor installed, you must first upgrade to NPM 10 and then upgrade to APM 3.5 before you can upgrade to SAM 5.0 and higher.

If you have version 3.5 of Application Performance Monitor installed, upgrade both NPM and APM on your current SolarWinds Server, in that order. Failure to upgrade in the correct order will result in the Configuration Wizard generating a Database Configuration Failure error.

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.

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:


  • Some charts may improperly display data as Date/Time when exporting to HTML.
  • An incorrect component status is displayed when the "Count statistic as difference" is enabled for SNMP Monitors.
  • SQL databases with a status of Critical are not displayed in Network Atlas.
  • Account Limitations does not work for Application Custom Properties.
  • Some AppInsight for SQL resources do not load correctly in Internet Explorer 7.
  • The threshold variables ${Threshold-Statistic-Warning}, and ${Threshold-Statistic-Critical}, do not work properly when alerting for Multi-value script monitors.

Fixed Issues and Additions in this Release

This release of SAM includes the following fixes and additions:

Version 6.0

Additions and Improvements:


  • AppInsight for SQL added.
  • Asset Inventory added.
  • Baseline and Threshold calculation added.
  • Real Time Event Viewer added.
  • User Auditing added.
  • Web Console based Report Writer added.
  • Server Warranty Information Resource added.
  • New Script Macros added.
  • Top XX Monitored Processes by I/O Reads/Sec Information Added.

Newly Added and Updated Application Templates:

    • Microsoft Windows Server 2012 Failover Cluster
    • Exchange 2010 Statistics with PowerShell
    • BizTalk Server 2010 Statuses through WMI
    • Microsoft Lync Server 2013 (Front-End Role)
    • Microsoft Lync Server 2013 (Edge Role)
    • Microsoft Lync Server (Mediation Role)
    • SharePoint Server 2013
    • Apache (Windows)
    • Veeam Backup and Replication Server
    • HTTPS Monitor
    • Kiwi Syslog Server
    • Orion Server
    • Windows Server 2003-2012 Services And Counters
    • SQL Server 2005 Analysis Services
    • SQL Server 2008 Analysis Services
    • SQL Server 2012 Analysis Services

Fixed Issues:


  • SAM now respects custom view settingsa
  • SAM tooltips on alert page are now working properlyb
  • Alerts now fire previously missing trigger optionsc
  • Fixed: Browser hangs when selecting test noded
  • Fixed: Single group view creation assigned to accounts not workinge
  • An issue with custom charts not showing data has been fixedf
  • An issue with HTTP Form Login Monitors not working has been fixedg
  • An issue concerning the listing of resources and events not appearing has been fixed.h
  • A SAM Database Maintenance issue has been fixed.i
  • A issue concerning JMX Bridge Failing has been fixed.j
  • An issue concerning Linux application alerts bouncing between Unknown and Up with the error "Connection Timeout. Job canceled by scheduler" has been fixed.k
  • An issue with running a Linux Script via SSH has been resolved.l
  • An issue with MinMaxAvgStatisticData showing future month and day has been fixed.m
  • An issue with the UPS Template has been fixed.n
  • An issue wher multi-statistic scripts behave erratically when text or NaN values are added to statistics has been fixed.o
  • An issue where Hardware health sensors vanish on reboot has been fixed.p
  • An issue where different status-displays in SAM and Network Atlas has been fixed.q
  • An issue where the Custom Chart (Min/Max/Average bps In/Out) reports inaccurate values has been fixed.r
  • An issue where charts are displaying inaccurate values has been fixed.s
  • An issue with the Multi Object Chart not handling certain configurations correctly has been fixed.t
  • An issue with the charts loading slowly has been fixed.u

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 431058 209460
b 386852 177012
c 415082 195665
d 429666 210968
e 363284 158324
f 455279 229879
g 447312 230766
h 463048 235922
i 462573 236146
j 434010 213959
k 413098 196156
l 422667 206290
m - 223179
n 460447 236649
o 455430 229296
p 450621 225974
q 458308 241820
r 462230 235635
s 443849 232158
t 480499 246409
u 458633 232156


Last modified