Network Management

A Network Node was not selected

This article describes an issue where a message on the Node Details or custom properties pages read: "A Network Node was not selected"

First published date

11/29/2018 10:59 PM

Last published date

2/26/2025 3:52 AM

Overview

his article describes an issue where a message on the Node Details or custom properties pages read: "A Network Node was not selected"

Sample Images:
 

ANetworkNodeWasNotSelected.PNG
image.png

The Node Status may also say Node is Unknown. 

Product section

Network Performance Monitor

Cause

1. The node has an incorrect polling EngineID.
2. Problem with one or multiple of the Web Servers.

Resolution

Resolution1:

Using the Orion Database Manager:
 
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)
-- Scripts are not supported under any SolarWinds support program or service.
-- Scripts are provided AS IS without warranty of any kind. SolarWinds further
-- disclaims all warranties including, without limitation, any implied warranties
-- of merchantability or of fitness for a particular purpose. The risk arising
-- out of the use or performance of the scripts and documentation stays with you.
-- In no event shall SolarWinds or anyone else involved in the creation,
-- production, or delivery of the scripts be liable for any damages whatsoever
-- (including, without limitation, damages for loss of business profits, business
-- interruption, loss of business information, or other pecuniary loss) arising
-- out of the use of or inability to use the scripts or documentation.

SELECT TOP 1000 *
FROM [NodesData]
WHERE [NodeID] = '9'
4. Replace 9 with the correct NodeID
5. 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:

-- Scripts are not supported under any SolarWinds support program or service. 
-- Scripts are provided AS IS without warranty of any kind. SolarWinds further 
-- disclaims all warranties including, without limitation, any implied warranties 
-- of merchantability or of fitness for a particular purpose. The risk arising 
-- out of the use or performance of the scripts and documentation stays with you. 
-- In no event shall SolarWinds or anyone else involved in the creation, 
-- production, or delivery of the scripts be liable for any damages whatsoever 
-- (including, without limitation, damages for loss of business profits, business 
-- interruption, loss of business information, or other pecuniary loss) arising 
-- out of the use of or inability to use the scripts or documentation.

SELECT TOP 1000 *
FROM [NodesData]
WHERE [EngineID] != '1'

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

Resolution 2:

1. Access each Web Servers URL to identify which Web Server is causing the problem.
2. Restart Orion Services of the affected Web Server/s.