Submit a ticketCall us

Have You Auto Renewed? If not, you're missing out.
The SolarWinds Renewal Program comes with a host of benefits including the most recent product updates, 24/7 technical support, virtual instructor-led training and more. Experience all of this with the convenience of Auto Renewal, and never worry about missing any of these great benefits. Learn More.

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

SAM 6.2.2 Release Notes

Updated 9/22/2015

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

 

Installing this Version

As with all modifications to your production environment, we recommend 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 Guide

Warnings:

  • 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.
  • Ensure your Orion products are compatible with each other by referring to the Orion Compatibility Matrix, found here: Compatibility of SolarWinds Orion products for installation and upgrade and End of Life Support

 

Upgrading and Configuring

If you have both NPM and APM installed, upgrade NPM on all SolarWinds servers first, and then on the additional 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 and Application Monitor" in the SolarWinds Server and 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.

Notes:
If you are installing/upgrading to SAM 6.2 or higher, Enterprise Operations Console (EOC) will need to be upgraded to version 1.6.2. The EOC upgrade can be found in your customer portal.
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.
SAM 6.2.1 and higher is compatible with the Federal Information Processing Standard (FIPS).
SolarWinds SAM 6.2.1 and higher support the following versions of SQL Server:
  • SQL Server 2008 without SP, with SP1, SP2, SP3, or with SP4.
  • SQL Server 2008 R2 without SP, with SP1 or SP2.
  • SQL Server 2012 without SP, with SP1, or with SP2.
  • SQL Server 2014.

 

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 Success Center article: Migrate credentials when upgrading Orion APM 3.5 to Orion APM 4.0 on a new server

 

Open Issues in Server and Application Monitor (Version 6.2.2):

Open Issue
None.

Fixed Issues and New Additions for Server and Application Monitor (Version 6.2.2):

Fixed Issues Customer Case Number
A problem with reporting the correct serial number for Dell nodes configured to use WMI via Asset Inventory has been fixed. 790564
An issue where an additional polling engine was unable to correctly communicate using an agent while running PowerShell scripts has been fixed. 777085 
Improper calculation of values for the following database performance counters in AppInsight for SQL application template has been fixed: Average Read Latency, Average Write Latency, Average Bytes/Read, Average Bytes/Write 809727
The following performance counter has been removed from the AppInsight for Exchange template: Average Document Indexing Time. 742221, 785049

 

Fixed DPAO Issues in this Release:

Fixed Issues

  • The Database Instance tooltip in the Database Performance Analyzer Orion Integration Module now displays the correct Wait Time.
  • A message displayed on the Database Instance Details screen regarding connectivity issues has been clarified. The updated message describes the issue and provides instructions for fixing the problem.
  • When the Database Performance Analyzer Orion Integration wizard runs, all relationships whose status has changed since the previous run are displayed for review.
  • In the Database Performance Analyzer Orion Integration wizard, the Filter button on the Review Relationships panel now works correctly .
Known Issues Workarounds

When the Database Performance Analyzer Orion Integration Module is installed, an error similar to the one below appears in the DPA log each time a user selects Test Connection:

ERROR (2015-08-31 11:10:06,807.CEST) [http-8124-3] DefaultIgniteExceptionLogger - An unexpected error occurred from 
com.solarwinds.dpa.orion.integration.OrionIntegrationManagerImpl.testConnection
com.solarwinds.common.swis.client.JsonHttpCallException: Call failed with status 403
  at com.solarwinds.common.swis.client.Swis.callJsonHttpPost(Swis.java:407)
  ...

Product functionality is not affected. Ignore this error.
When the Database Performance Analyzer Orion Integration Module is installed, JavaScript errors appear in the console when a user mouses over the Blockers in the Last Hour resource. Product functionality is not affected. Ignore the errors.
When the Database Performance Analyzer Orion Integration Module is installed on AddWebsite, the database is not configured. Also install the module on the main poller.
When the Database Performance Analyzer Orion Integration Module is installed, availability groups on monitored SQL Server database instances are not mapped correctly on the Orion platform. Run the Update Connection Information wizard and specify the virtual IP address of the availability group listener.


Fixed QoE Issues in this Release:

Fixed Issue

The QoE module is now offered free of charge.

Release Notes History:
SAM 6.2.1
SAM 6.2
SAM 6.1.1
SAM 6.1
SAM 6.0.2
SAM 6.0.1
SAM 6.0
SAM 5.5
SAM 5.2 SP1
SAM 5.2

 

Last modified

Tags

Classifications

Public