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) > NCM search in 7.4 giving "Indexing in progress 0% complete" caused by NCM-NPM nodes not being in sync

NCM search in 7.4 giving "Indexing in progress 0% complete" caused by NCM-NPM nodes not being in sync

Created by Adrian Cook, last modified by MindTouch on Jun 23, 2016

Views: 132 Votes: 2 Revisions: 3

Overview

 

Search not working in NCM 7.4 because "Indexing in progress 0% complete".

To verify that the steps in this article apply to you

  1. Open the log adjuster tool: click Start > All Programs > SolarWinds Orion > Documentation and Support > Log Adjuster.
  2. Set the NCM Business Layer to Debug and select Apply.
  3. Click Settings > NCM settings > Seach Settings and disable and then enable the Search.
  4. Go to C:\ProgramData\Solarwinds\Logs\Orion\NCM and open NcmBusinesslayerPlugin.log and look for the DEBUG messages below:

 

276 [3] DEBUG SolarWinds.NCM.FTS.Search.ConfigChangeNotificationProvider - NCMSearch: Listen Tick - Delay:100 ScanPeriod:60000


276 [3] DEBUG SolarWinds.Orion.Common.SqlHelper - SQL: SELECT OptionValue
FROM NCM_Options

WHERE OptionName=@optionName (@optionName=NCMConfigIndexStatus)


280 [3] DEBUG SolarWinds.NCM.FTS.Search.ConfigChangeNotificationProvider - NCMSearch: Listen Tick: - Nodes are not synchronized. Skip listen

 

If you see "Nodes are not synchronized. Skip listen" then follow the steps below.

Environment

  • NCM 7.4.x

 

Cause 

 

The issue is caused because the NPM and NCM Nodes are not synchronized.

Resolution

  1. Go to the Orion database and run the following query:

update WebSettings set SettingValue=(select OptionValue from NCM_Options where OptionName='NCM.NodesSyncID71')
where SettingName='NCM.NodesSyncID71'

  2. After a few minutes of running the query, click Settings > NCM settings >Seach Settings and disable and then enable the Search.

  3. The indexing should start progressing and when it is finished you can search the NCM configs.

 

 

 

 

Last modified
21:26, 22 Jun 2016

Tags

Classifications

Public