Submit a ticketCall us

Don’t fall victim to a ransomware attack
Backups are helpful, but sometimes that’s not enough to protect your business against ransomware. At our live webcast we will discuss how to protect against ransomware attacks with SolarWinds® Patch Manager and how to leverage log data to detect ransomware. Register now for our live webcast.

Home > Success Center > Network Performance Monitor (NPM) > Limitation propagates to newly cloned view

Limitation propagates to newly cloned view

Updated December 1, 2016

Overview

This article provides brief information and steps to resolve the issue when a view with limitation is cloned.  The limitation is propagated to a new clone view.

 

For example, when view1 is clone [View1(2), View1(3) and View1(4)]. The limitation is copied to all these views.
By default, the limitation should NOT get copied or cloned.

Environment

  • NPM 11.5.2
  • NPM 11.5.3
  • NPM 12.0

Cause

The issue occurs after an upgrade from NPM 11.5.3 to NPM 12.0.

Resolution

Workaround:

1. Delete the limitation first for the view you need to clone. 
2. Put the limitation back.

 

 

 

Last modified
01:18, 1 Dec 2016

Tags

Classifications

Public