Submit a ticketCall us

Webinar: Web Help Desk for HR, Facilities and Accounting Departments
This webinar will focus on use cases for HR, Facilities and Accounting.

Having a unified ticketing and asset management system for all the departments in your company can provide end-users with a seamless experience and make things easier for your IT team. Yet, with different business tasks and objectives, many departments don’t fully understand the capabilities of Web Help Desk and how the software can be customized for effective use in their departments.
Register Now.

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