Submit a ticketCall us

Training ClassSign up for Network Performance Monitor (NPM) and Scalability instructor-led classes

Attend our instructor-led classes, provided by SolarWinds® Academy, to discuss the more advanced monitoring mechanisms available in NPM as well as how to tune your equipment to optimize its polling capabilities. NPM classes offered:
NPM Custom Monitoring and Polling
Orion Platform Scalability

Reserve your seat.

Home > Success Center > Network Performance Monitor (NPM) > NPM - Knowledgebase Articles > 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,174 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

Tags

Classifications

Public