Network Management

Large report error: Unexpected Website Error "Request timed out' in the SolarWinds Platform

This article shows how to resolve the issue when generating more extensive reports on manual execution of a Schedule Report, and the SolarWinds Platform Web Console returns a message, Unexpected Website Error Request timed out.

First published date

10/19/2018 8:33 PM

Last published date

5/20/2025 10:06 PM

Overview

When generating larger reports on a manual execution of a Schedule Report, the SolarWinds Platform Web Console returns a message:
 

Unexpected Website Error
Request timed out.


The report email may eventually be sent after the error is displayed, but this doesn't always happen.
 

image.png

Product section

Network Performance Monitor

Cause

  • This error can occur when attempting to preview a very large report in the SolarWinds Platform Web Console then timed out.
  • The report attached on the Schedule Report is still on ReportWriter (Deprecated) Type

Resolution

If the report attached on the Schedule Report is still on ReportWriter (Deprecated) Type. First, migrate the report using the SolarWinds Legacy Reports Migration Tool. Check if the same Unexpected Website Error Request timed out message is encountered. If the issue still occurring, proceed below:

  • RDP to the Main Polling Engine
  • Locate the web.config file (C:\inetpub\SolarWinds) and create a back-up before editing. For SolarWinds Platform version 2022.x or later, the web.config file is on a new location (C:\Program Files (x86)\SolarWinds\Orion\Web) by default or depending on your installation path (<Install Path>\SolarWinds\Orion\Web).
  • Run the Notepad as Administrator and open the web.config file
  • Increase the current executionTimeout="XXXX" to executionTimeout="3600" for the following elements:
    • Orion/ReportWait.aspx
    • Orion/Report.aspx
    • Orion/Reports/AsExcel.aspx
    • Orion/Reports/Preview.aspx
    • Orion/Reports/Scheduler.aspx
  • After making the changes, it should look similarly like this:
<location path="Orion/ReportWait.aspx">
<system.web>
<httpRuntime maxRequestLength="16096" executionTimeout="3600" />
</system.web>
</location>
<location path="Orion/Report.aspx">
<system.web>
<httpRuntime maxRequestLength="16096" executionTimeout="3600" />
</system.web>
</location>
<location path="Orion/Reports/AsExcel.aspx">
<system.web>
<httpRuntime maxRequestLength="64384" executionTimeout="3600" />
</system.web>
</location>
<location path="Orion/Reports/Preview.aspx">
<system.web>
<httpRuntime maxRequestLength="16096" executionTimeout="3600" />
</system.web>
</location>
<location path="Orion/Reports/Scheduler.aspx">
<system.web>
<httpRuntime maxRequestLength="16096" executionTimeout="3600" />
</system.web>
</location>
  • Save the web.config file and perform a quick Shutdown and Restart of all SolarWinds Services which will include the Websites for changes to take effect.
  • Verify if the issue is still occurring.

NOTE: The web.config file will get overwritten in cases like rebuilding the SolarWinds Platform Website since part of the process is renaming and recreating the C:\inetpub\SolarWinds or <Install Path>\SolarWinds\Orion\Web folder in which the web.config file resides. It will need to change that new web.config file by again increasing the executionTimeout="3600" for the above elements.