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 Configuration Manager (NCM) > NCM - Knowledgebase Articles > Nodes missing from the NCM Configuration Management View

Nodes missing from the NCM Configuration Management View

Created by Marjune Obana, last modified by Martin Tully on Jul 24, 2017

Views: 2,377 Votes: 4 Revisions: 19

Overview

The NCM nodes are not visible in the Configuration Management tab after upgrading to NCM 7.3 or later. Nodes are showing in an NCM desktop application and in the NCM Summary view but they remain to be missing in the Configuration Management view. 

 

Note: NCM desktop application is discontinued from NCM 7.4

Environment

  • NCM 7.3 and later

Cause

Custom properties that are common to default NCM properties cause the schema to be corrupted and nodes cannot be displayed.

Sample Information Service log: (C:\ProgramData\Solarwinds\InformationService\v3.0)

2014-06-16 17:21:42,779 [6] ERROR SolarWinds.InformationService.Core.InformationService - Exception caught in method RunQuery
SolarWinds.Data.Query.ParserException: Ambiguous column name VirtualMachine between entities Orion.Nodes and Orion.NodesCustomProperties.

Resolution

Based on the sample logs above, you have a node custom property called Virtual machine and it is breaking the NCM query. To resolve this you can simply delete offending Custom Property:

  1. Log in to your Orion Web Console using admin account
  2. Go to Settings
  3. Go to Manage Custom Properties
  4. Find offending Custom Property (in example VirtualMachine)
  5. Select it
  6. Click on Delete and confirm deletion

 

In order to retain current Custom Property values refer to Change the Custom Property name.

 

Note:

  • Make sure that the Custom Property names do not use common terms found in the database such as router, engine, switch, IP and so on. 
  • More information and other users' experience on this topic you can find in Thwack article - "Missing" nodes and NCM 7.3 upgrade issues
Last modified

Tags

Classifications

Public