Submit a ticketCall us

Training ClassSign up for Network Performance Monitor (NPM) and Scalability instructor-led classes

Attend our instructor-led classes, provided by SolarWinds® Academy, to discuss the more advanced monitoring mechanisms available in NPM as well as how to tune your equipment to optimize its polling capabilities. NPM classes offered:
NPM Custom Monitoring and Polling
Orion Platform Scalability

Reserve your seat.

Home > Success Center > Network Performance Monitor (NPM) > NPM - Knowledgebase Articles > Unexpected error when manually running a scheduled report

Unexpected error when manually running a scheduled report

Created by Roman.Castro, last modified by Abdul.Aziz on Sep 03, 2018

Views: 1,910 Votes: 0 Revisions: 5

Updated Sept 3, 2018

Overview

In general scheduled reports not running OR a specific scheduled report was not received and after running it manually from the Orion Web Console, it displays an Unexpected Error message. 

Environment

  • Any NPM version

Resolution

Restart All Orion services via Orion Service manager Desktop App. Wait for 10 minutes and try the scheduled report again. If this does not help, follow below troubleshooting steps:

 

  1. Verify if you are using additional web servers.
    1. Check IIS.
    2. Check the Websites table.
      SELECT TOP 1000 * FROM [dbo].[Websites]
    3. Check the ReportJobs table to see what WebsiteID does the Report is configured to.
      SELECT TOP 1000 * FROM [dbo].[ReportJobs]
  2. Look for the URL of the Orion website (FQDN or IP).
  3. Access the Orion Web Console using the IP address of the primary website or additional website and run the report.

 

If this works, then it could be a DNS issue, bindings or load balancer issue on the environment.

 

Another Workaround:

  1. Access the Orion Web Console via the IP address of a specific AWS and run the report.
  2. Configure all the reports to use a specific Website (WebsiteID).

 

Last modified

Tags

Classifications

Public