Submit a ticketCall us

WebinarVisual Monitoring Tactics: Getting More Log Search Value from SolarWinds Log & Event Manager with nDepth Webcast

Do things seem to make more sense when they are visualized? Are you an IT professional or security expert with a wish for more cybersecurity tools that provide an intuitive visual experience? Join Alexis Horn and Jamie Hynds from SolarWinds as they demonstrate how the nDepth feature in LEM can help make visualizing log search results a reality.

Register now.

Home > Success Center > Network Configuration Manager (NCM) > NCM - Knowledgebase Articles > NCM jobs stop running after a server migration

NCM jobs stop running after a server migration

Created by Mariusz Handke, last modified by Steven Bansil_ret on Jul 05, 2016

Views: 801 Votes: 1 Revisions: 7

Overview

After you migrate SolarWinds® Network Configuration Manager (NCM) to another server, the NCM jobs stop running. 

Environment

NCM version 7.2.2 and earlier

Cause 

The Orion (Core) server is referencing the previous NCM server. 

Resolution

  1. Log in to your Orion server as an administrator. 
  2. Open the Orion Service Manager by clicking Start > All Programs > SolarWinds Orion > Advanced Features > Orion Service Manager.
  3. Stop all services.
  4. Open the Orion Database Manager.
  5. Select the Orion database.
  6. Right-click the Orion database and select New Query.
  7. In the right pane, enter the following syntax, and click Execute Query:

    DELETE FROM PendingNotifications

  8. In the right pane enter the following syntax, and click Execute Query:

    DELETE FROM Subscriptions

  9. Start all services.

    In the Orion Service Manager, click Start Everything. This process my require several minutes to complete.

  10. Verify that your NCM jobs are executing properly.

 

 

Last modified

Tags

Classifications

Public