Submit a ticketCall us

Announcing NCM 7.7
With NCM 7.7, you can examine the rules that make up an access control list for a Cisco ASA device. Then you can apply filters to display only rules that meet the specified criteria, order the rules by line number or by the hit count, and much more.
See new features and improvements.

Home > Success Center > Network Performance Monitor (NPM) > NPM 12 upgrade fail as it detect NCM is still on NCM 7.2.2 even when NCM is already on NCM 7.4

NPM 12 upgrade fail as it detect NCM is still on NCM 7.2.2 even when NCM is already on NCM 7.4

Created by Malik Haider, last modified by Malik Haider on Jan 19, 2017

Views: 45 Votes: 4 Revisions: 8

Updated June 16, 2016

Overview

This article provides brief information and steps to resolve the issue when your NPM upgrade fails. 

NPM 12 upgrade fail as it detect NCM is still on NCM 7.2.2 even when NCM is already on NCM 7.4

 

 

 

 

The Web console  7.4 is installed: 

 

 

The programs and feature we found the NCM 7.4 is installed so there is no issue with the installation:

 

 

Environment

NPM version12 

Cause 

There must be some registry entry left with the previous installation what we found here is NCM-NPM Integration were not deleted 

 

 

 

Possible Resolution(s)

Remove installed program from Registry:

  • Click Start > Run, and enter regedit.
  • Go to HKEY_CLASSES_ROOT\Installer\Products. 
  • Check if there is any entry:

 

Remove program via command line

  • Consult with SolarWinds Support to find proper registry key
  • Use  msiexec /x command with proper registry key to uninstall product via 'Run as Administrator' command line.  

 

 

4. Re-run the installer.

 

The issue should now be resolved. 

 

 

 

Last modified
09:36, 19 Jan 2017

Tags

Classifications

Public