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 > Network Performance Monitor (NPM) > Reboot alert does not trigger or send e-mail messages on nodes

Reboot alert does not trigger or send e-mail messages on nodes

Updated April 3, 2017

Overview

This article provides steps to resolve a reboot alert that stopped working, which is a known issue on NPM 12.x

Reboot alert no longer triggers or sends e-mail messages.

Environment

Orion Platform 2016.x and later versions

Resolution
1. Upgrade to NPM 12.1 and install OrionPlatform-v2017.1.5300-MSP-HotFix2

 

Workaround 1

  1. Perform a Remote Desktop Protocol (RDP) session to the Orion server.
  2. Go to C:\Windows\Temp\SolarWinds\JobEngine.v2.
  3. Check for stale data. All ShadowCopyCaches should show present timestamp.
  4. Delete all old ShadowCopyCache folders.
  5. Restart services for both Job Engine v1 and Job Engine v2.
  6. Perform a test reboot on a node to verify the reboot alert triggers.

 

Workaround 2

  1. Go to ORIONSERVERHOSTNAME/Orion/Admin/AdvancedConfiguration/Global.aspx
  2. Find "PubSubMaxQueueItemsCount" and set it to 0
  3. Click Save 
  4. Perform a test reboot on a node to verify the reboot alert triggers.

 

 

 

 

Last modified

Tags

Classifications

Internal Use Only