Submit a ticketCall us

Get a crash course on Network Monitoring delivered right to your inbox
This free 7-day email course provides a primer to the philosophy, theory, and fundamental concepts involved in IT monitoring. Lessons will explain not only how to perform various monitoring tasks, but why and when you should use them. Sign up now.

Home > Success Center > Network Performance Monitor (NPM) > SolarWinds Orion Platform 2016.2 Hotfix 1

SolarWinds Orion Platform 2016.2 Hotfix 1

Created by Milton Harris, last modified by Su-Lyn Rosenberry on Mar 01, 2017

Views: 136 Votes: 1 Revisions: 12

Updated Dec 13, 2016

Aren't sure if this is the latest hotfix? Go to the Orion Platform hotfix release page or to your product's release notes to review available hotfixes.

Fixed issues

This hotfix addresses the following issues:

  • Group limitations are not applied to event resources.

  •  After an upgrade or migration, the OrionServers table has two records for the main polling engine. This results in incorrect license assignments.
  • Queries to Orion.Module and Orion.ModuleGlobal fails. SWIS log will contain messages similar to the following text:

System.NullReferenceException: Object reference not set to an instance of an object.           SolarWinds.Data.Providers.Orion.ModuleTable.CreateTableScan (IProductLicense x)

   at System.Linq.Enumerable.Any[TSource](IEnumerable`1 source, Func`2 predicate)

   at SolarWinds.Data.Providers.Orion.ModuleTable.<CreateTableScan>d__6.MoveNext()

  • Polling using agents does not work when a node uses NAT IP.
  • When you have multiple polling engines and some of them are down, queries to Orion.ModuleGlobal take too long, and might result in website timeouts.
  • Agents are not enabled to start at boot with older versions of Linux, such as SUSE-12.1.
  • The ServiceNow alert action fails to pull state choices, and the state field required for ServiceNow integration is not present on an incident entity. The following error is returned: 

Error querying ServiceNow Instance Instance can be offline or not properly configured.

  • If a custom property is created and applied to an application, views with group limitations do not display the application.
  • An agent cannot connect to the Orion server from a Linux-based computer because the agent changed the Orion hostname to an unresolvable string.

 

Environment

  • NPM 12.0.1
  • SAM 6.3
  • NCM 7.5.1
  • SRM 6.3
  • Patch Manager 2.1.3
  • VNQM: 4.2.4

Notes

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

Installation instructions

  1. Download the hotfix from your Customer Portal.
  2. Log in to the server that hosts your SolarWinds Orion installation using an administrator account.
  3. Run the Orion Service Manager, click Shutdown Everything, and close the Orion Service Manager.
  4. Run the OrionPlatform-v2016.2.5300-HotFix1.exe file, and follow the instructions in the installation wizard.


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

Uninstallation instructions

  1. Log in to the server that hosts your SolarWinds Orion installation using an administrator account.
  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 2016.2 v116.2.5300 (B1007)", click Uninstall, and complete the uninstallation wizard.

 

Last modified
11:42, 1 Mar 2017

Tags

Classifications

Public