Submit a ticketCall us

Webinar: Web Help Desk for HR, Facilities and Accounting Departments
This webinar will focus on use cases for HR, Facilities and Accounting.

Having a unified ticketing and asset management system for all the departments in your company can provide end-users with a seamless experience and make things easier for your IT team. Yet, with different business tasks and objectives, many departments don’t fully understand the capabilities of Web Help Desk and how the software can be customized for effective use in their departments.
Register Now.

Home > Success Center > Network Configuration Manager (NCM) > 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: 260 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
13:45, 24 Jul 2017

Tags

Classifications

Public