Submit a ticketCall us
Home > Success Center > Network Performance Monitor (NPM) > Orion Platform 2017.1 Hotfix 3

Orion Platform 2017.1 Hotfix 3

Updated July 14th, 2017

 

SolarWinds Orion Platform 2017.1 Hotfix 3 addresses the following issues:

  • An additional line is added to a cron job after every Orion agent upgrade, leading to overloading the machine.
  • RabbitMQ log files are large.
  • Invalid Active Diagnostics checks that prevent installation.
  • Menu items disappear after upgrade.
  • Scheduled alerts trigger during different time periods when the time zone is uses Daylight Savings Time in the southern hemisphere.
  • The SolarWinds Recommendations service is not stopped when installing NPM over SAM on the same version of the Orion Platform.
  • Improved the PackageCleaner’s reliability. 
  • Deadlocks and locking in the OrionServers table.

The hotfix is cumulative with SolarWinds Orion Platform 2017.1 Hotfix 2 that addresses the following issues:

  • Volume statistics on Linux machines polled by agents are missing.
  • Mitigates issue with syntax errors in system log on some Ubuntu agent machine.
  • SWIS memory leak from the QueryExecutionContextExtensions.Extensions cache.
  • Intermittent outages based on SWIS ExpandedLimitations indications flooding pub/sub.
  • Automatic monitoring settings are reset to the default after the Configuration Wizard runs.
  • Deadlocks and locking in the OrionServers table.

The hotfix is cumulative with SolarWinds Orion Platform 2017.1 Hotfix 1 that addresses the following issues:

  • Volume monitoring stops.
  • The Node Reboot alert does not trigger.
  • SNMPv3 credentials are not correctly assigned to nodes.
  • SNMPv3 credentials can be deleted or incorrectly updated when mass editing nodes that use different polling methods.
  • Vulnerability on a weak cipher suite on the TLS channel for 64-bit ciphers (SWEET32).
  • Upgrade to NPM 12.1 with NTA 4.2.1 fails with this error:  No valid package combination was found for current system.
  • PackageCleaner ignores MSP files.
  • ServiceNow integration stops working if you mass edit incidents.
  • Incidents in ServiceNow reactivate.
  • Unable to collect diagnostic ZIP files that exceed 4 GB.
  • Unable to enter a description and attach data in the diagnostics tool.
  • Network Atlas maps load slowly or do not load.
  • Manually added component monitors to existing application monitors do not appear in PerfStack.
  • WMI critical component monitor does not display in PerfStack.

Environment

Apply this hotfix if you run any of the following SolarWinds products: 

  • NPM 12.1
  • SAM 6.4
  • NCM 7.6
  • SRM 6.4
  • Patch Manager 2.1.4
  • VNQM 4.4
  • VIM 7.1

Notes

  • This hotfix requires SolarWinds Orion Platform 2017.1.
  • This hotfix must be installed on the main polling engine, on any additional polling engines or web servers, and High Availability servers.
  • This hotfix addresses the issues for all SolarWinds Orion Platform products. 

Installation

  1. Use an Administrator account to log in to the server that hosts your SolarWinds Orion installation.
  2. Download the hotfix from your Customer Portal.
  3. Run the Orion Service Manager, click Shutdown Everything, and close the Orion Service Manager.
  4. Run the OrionPlatform-v2017.1.5300-HotFix3.exe file, and follow the instructions in the installation wizard.

After applying this fix, the issues outlined in the description should no longer occur.

Install the Hotfix with SolarWinds HA

Important: The HA pool must be disabled to begin installation. If you install prior to 
disabling, the pool is automatically disabled.

  1. In the Orion Web Console, click Settings > All Settings > High Availability Deployment Summary.
  2. Select the pool you want to disable.
  3. Toggle High Availability to Off.
  4. Install the hotfix on the primary server in the pool.
  5. Install the hotfix on the secondary server in the pool.
  6. In the Orion Web Console, click Settings > All Settings > High Availability Deployment Summary.
  7. Select the pool you want to enable and toggle High Availability to On.

The Orion Web Console verifies all SolarWinds product versions match across the HA pair 
before enabling. If you receive errors, check your product versions.

You may need to recreate the HA pool.  For details, see Set up an HA pool.

Uninstallation

  • You may need to run the Configuration Wizard manually after uninstalling the hotfix.
  • You may need to reinstall Active Diagnostics by running the installer from this folder: C:\ProgramData\SolarWinds\Installers

 

  1. Use an Administrator account to log in to the server that hosts your SolarWinds Orion installation.
  2. Run the Orion Service Manager, click Shutdown Everything, and close the Orion Service Manager.
  3. Navigate to Control Panel > Programs > Programs and Features > View installed updates.
  4. Select "Update for SolarWinds Orion Core Services 2017.1 v117.1.5300.1825 (HotFix3)", click Uninstall, and complete the uninstallation wizard.
  5. Select "Update for SolarWinds Orion Network Atlas v1.16.0 (B41)", click Uninstall, and complete the uninstallation wizard.
  6. If you installed Hotfix 2, select "Update for SolarWinds Information Service v2017.1.1.430 (HotFix2)", click Uninstall, and complete the uninstallation wizard. You will need to reinstall hotfix 2.
Last modified

Tags

Classifications

Public