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 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,115 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