Submit a ticketCall us

ebook60.pngHow to be a Cisco® ASA ace

Our eBook, Thou Shalt Not Pass…I Think?! can help you overcome the challenges of monitoring and managing Cisco ASA firewalls. This eBook is a great read if you’ve been frustrated with monitoring firewalls, managing ACL configs, and troubleshooting VPN connections.

Get your free eBook.

Home > Success Center > Network Performance Monitor (NPM) > Basic alerts failure after upgrading NPM

Basic alerts failure after upgrading NPM

Table of contents

Updated October 4th, 2017

Issue

After an NPM upgrade, basic alerts fail to trigger the email.

Cause

The registered component object model (COM)-based components may be corrupted.

Resolution

Re-register the COM components to re-enable the basic alert actions:

  1. Stop the Orion Services - How to Start/Stop Orion Services.
  2. Click Start > Run > Type CMD, to open command prompt.
  3. Change directory to C:\Program Files (x86)\SolarWinds\Orion, and then type the command:

    OrionAlertEngine.exe /regserver
  4. Change directory to C:\Program Files (x86)\SolarWinds\Common, and then type the command:

    regsvr32 SWAlertActions.dll
  5. Start the Orion Services - How to Start / Stop Orion Core Services
  6. To verify that basic alerts is working, run the OrionAlertEngine.exe file. This file is located in the Orion folder.

 

Applies to: NPM 11.0.1 and older.

Does not apply to: NPM 12.2 or newer, seems that OrionAlertEngine.exe is not in that file path so it must have been moved or pushed out in later releases.

Last modified

Tags

Classifications

Public