Submit a ticketCall us

Solarwinds & Cisco Live! Barcelona
Join us from the 29th of January to the 2nd of February at Cisco Live 2018 in Barcelona, where we will continue to show how monitoring the network with SolarWinds will keep you ahead of the game. At our booth (WEP 1A), we will demonstrate how SolarWinds network solutions can help. As a bonus, we are also hosting a pre-event webinar - Blame the Network, Hybrid IT Edition with our SolarWinds Head Geek™, Patrick Hubbard on January 24th - GMT (UTC+0): 10:00 a.m. to 11:00 a.m. There's still time to RSVP.

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: 1,210 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

Tags

Classifications

Public