Submit a ticketCall us

AnnouncementsFace your biggest database issues head-on

Our new eCourse helps you navigate SQL Server performance blocks by teaching you how to recognize and deal with the three DBA Disruptors: Performance Hog, Blame Shifter, and Query Blocker. Register today to learn how to defend your environment and fend off menacing disruptions.

Register for your free eCourse.

Home > Success Center > Network Performance Monitor (NPM) > NPM - Knowledgebase Articles > Changing the server name now results to multiple primary pollers

Changing the server name now results to multiple primary pollers

Created by Leif Amland, last modified by Rodim Suarez_ret on Jun 23, 2016

Views: 910 Votes: 0 Revisions: 3

Updated

Overview

If you change the name of your Orion server after an upgrade, you will notice multiple primary polling engines in the Engines table. They need to be cleared out and the nodes reassigned to the correct polling engine.

Environment

  • NPM 11.x
  • NPM 12.x

Cause 

Changing the name of a server during the upgrade caused multiple entries in the Engines table to be incorrect.

Resolution

  1. Stop all Orion Services using the Orion Service Manager.
  2. Open the Database Manager and load the default server.
  3. Navigate to the Engines table, right click and query table. At the top center window hit Execute.
  4. If you only have one Primary Polling Engine, there should only be one entry here.
  5. Enable Table editing at the top and remove the false entries.
  6. Start all Orion Services.

If you need to change the polling engine for the nodes, please see the following articles:

How to change polling engines without a SQL query

How to change polling engines using Database Manager

 

Last modified

Tags

Classifications

Public