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) > Basic alerts failure after upgrading NPM

Basic alerts failure after upgrading NPM

Table of contents
Created by Interspire Import, last modified by Jeremy Holmes on Jun 22, 2017

Views: 135 Votes: 2 Revisions: 16

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.

Last modified
12:57, 22 Jun 2017

Tags

Classifications

Public