Submit a ticketCall us

Announcing NCM 7.7
With NCM 7.7, you can examine the rules that make up an access control list for a Cisco ASA device. Then you can apply filters to display only rules that meet the specified criteria, order the rules by line number or by the hit count, and much more.
See new features and improvements.

Home > Success Center > Network Performance Monitor (NPM) > Unable to generate Wireless Heat Map

Unable to generate Wireless Heat Map

Updated June 22th, 2017

Overview

When the customer tries to generate a wireless heat map, the following errors are seen:

  • Automatic re-generation from [Date and time] was not successful. Try to generate in the Network Atlas manually and updated map will be visible here.
  • There is no available engine to process the WirelessHeatMap generation.

Environment

  • Network Performance Monitor
  • Windows Server

Cause 

Customer has subscription errors in the SQL database. The following error messages are discovered in the diagnostic files under LogFiles\InformationServiceV3:

 

[RetryNotifications] WARN  SolarWinds.InformationService.ChangeBroker.GroomingManager - (null)     The Change Broker has groomed 90 pending notifications because the total notifications exceeded 1000.
2015-12-01 22:21:19,936 [144] ERROR SolarWinds.InformationService.ChangeBrokerEvaluator.LegacyEngine.LegacyEvaluator - (null)     Subscription match handler failed with an exception. Indication: System.InstanceModified, SubscriptionId: 47c7bca6-26f3-49ed-a57b-8363f94ae148, Handler: System.Action`1[SolarWinds.InformationService.Addons.PubSub.EvaluatorNotification], Exception: System.InvalidOperationException: Subscription not found. SubscriptionId: 47c7bca6-26f3-49ed-a57b-8363f94ae148
   at SolarWinds.InformationService.ChangeBroker.Broker.HandleSubscriptionMatch(EvaluatorNotification notification)
   at SolarWinds.InformationService.ChangeBrokerEvaluator.LegacyEngine.LegacyEvaluator.ReportIndication(EvaluatorIndication evaluatorIndication)

Resolution

First try restarting Network Atlas. If that fails to resolve the issue proceed to steps below.

  1. Open the Orion Database Manager or the SQL Server Management Studio.
  2. Connect to the Orion Database.
  3. Shutdown all Orion Services using the Orion Service Manager.
  4. Run the following queries:
    • DELETE FROM PendingNotifications
    • DELETE FROM Subscriptions
  5. Restart all Orion services using the Orion Service Manager. 

 

 

 

Last modified
04:20, 22 Jun 2017

Tags

Classifications

Public