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) > Do not use the same name for a web-based and legacy report in NPM 12.0

Do not use the same name for a web-based and legacy report in NPM 12.0

Table of contents
Created by Lori Krell_ret, last modified by MindTouch on Jun 23, 2016

Views: 8 Votes: 0 Revisions: 3


Creating legacy versions of web-based reports sharing the same name can cause issues. If the web console locates a duplicated name for a report in a local file and a web-based report, the console throws a series of errors when displaying the report list.



  • NPM 12.0


When creating a copy of a web-based report, you should create the report as a web-based or legacy with a different name than the original report. The report list checks and displays a list of reports by name. If a legacy and web-based share the exact same name, the web console displays errors.


Always give a legacy report a different name than a web-based report to keep the issue from occurring.




Last modified
22:12, 22 Jun 2016