Submit a ticketCall us

Bridging the ITSM Divide
Integrated help desk and remote support software for faster resolution

Join us on Wednesday, November 29, 2017 at 11 a.m. CT, as we discuss the benefits of effectively integrating your help desk software with remote support solutions to help increase the efficiency of IT administration, improve communication, and decrease mean time to resolution (MTTR) for IT issues of all sizes. This directly impacts end-user satisfaction and your business’ bottom line. Register Now.

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: 75 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

Tags

Classifications

Public