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) > A Network Node was not selected

A Network Node was not selected

Created by Michael Osborn, last modified by MindTouch on Jun 23, 2016

Views: 67 Votes: 1 Revisions: 10



This article describes an issue where a message on the Node Details page reads A Network Node was not selected.


The Node Status may also say Node is Unknown


You may also get an error when trying to delete the node or change its polling method:



NPM 11.5 and later


The node has an incorrect PollingEngineID.


  1. Check the AllEngines table and note down the EngineID of one of the pollers.
  2. Open Database manager - Add default server - find your Solar Winds database - find the table "AllEngines" and double click on it, execute the default query "SELECT TOP 1000 * FROM [dbo].[AllEngines]"
  3. Check the NodesData table, and find the EngineID column. You can find it by running this query (you can find the node ID number by going to the node http://YourOrionServer/Orion/NetPerf...?NetObject=N:9)
    SELECT TOP 1000 * FROM [dbo].[NodesData] where NodeID = '9'
    Replace 9 with the correct node id
    Verify that it matches a valid poller EngineID. If it does not, correct it and you should be able to monitor the node properly.

Note: If you want to see all the nodes where EngineID is not found based on step 1, you can run the following:
         SELECT TOP 1000 * FROM [dbo].[NodesData] where EngineID != '1'

     Where '1' is returned from the query in step one


Last modified
21:47, 22 Jun 2016