Submit a ticketCall us

AnnouncementsTHWACKcamp 2018 is here

2018 is the seventh year for THWACKcamp™, and once again we’ll be live October 17 – 18 with packed session tracks covering everything from network monitoring and management, to change control, application management, storage, cloud and DevOps, security, automation, virtualization, mapping, logging, and more.

Register for online sessions.

Home > Success Center > Network Performance Monitor (NPM) > NPM - Knowledgebase Articles > After an upgrade, reports are not displaying on Additional Web Server

After an upgrade, reports are not displaying on Additional Web Server

Table of contents
No headers
Created by Interspire Import, last modified by MindTouch on Jun 23, 2016

Views: 1,178 Votes: 0 Revisions: 8

During an upgrade, reports and report schemas are not automatically moved from your primary Orion NPM server to your Orion Additional Web Server. The following procedure completes the required migration.

To migrate reports from a primary Orion NPM server to an additional web server, copy the following files from your Orion NPM Server to the corresponding location on your Additional Web Server:

  • The Orion Report Writer schema file: OrionReportWriter.schema
    Note: The default location for this file is C:\Program Files\SolarWinds\Orion\.
  • The Orion Reports folder
    Note: The default location for this folder is C:\Program Files\SolarWinds\Orion\Reports\.
If you have reports on additional polling engines that are not already stored on the primary polling engine, after completing an upgrade, these reports must be copied to the Orion Reports folder on the prmary polling engine (the default location for this folder is C:\Program Files\SolarWinds\Orion\Reports\). In NPM version 10.5 and higher, these reports will be stored in the database.

This article applies to:
All versions of Orion Network Performance Monitor

Last modified

Tags

Classifications

Public