Submit a ticketCall us

Looking to compare latest NPM features with previous versions of NPM?
The NPM new feature summary offers a comparison of new features and improvements offered with this release.

 

 

 

 

Home > Success Center > Network Performance Monitor (NPM) > NPM 12 install fails because of old SRM install

NPM 12 install fails because of old SRM install

Created by Michael Almadova, last modified by MindTouch on Jun 23, 2016

Views: 1,018 Votes: 1 Revisions: 6

Updated June 13, 2016

Overview

This article provides brief information and steps to resolve the issue when NPM 12 upgrade fails because of old SRM data found in the database and server registry.

 

Environment

NPM version 11.x and 12

Cause 

SRM registry key and old SRM database tables that still exist. 

Resolution

  1. Drop all SRM tables from the database. Work with a DBA to write a query to remove all SRM_ tables located in the database.
  2. Delete the following registry key:

HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\SolarWinds\Orion\SRM 

 

 

 

 

Last modified
22:54, 22 Jun 2016

Tags

Classifications

Public