Submit a ticketCall us

Solarwinds & Cisco Live! Barcelona
Join us from the 29th of January to the 2nd of February at Cisco Live 2018 in Barcelona, where we will continue to show how monitoring the network with SolarWinds will keep you ahead of the game. At our booth (WEP 1A), we will demonstrate how SolarWinds network solutions can help. As a bonus, we are also hosting a pre-event webinar - Blame the Network, Hybrid IT Edition with our SolarWinds Head Geek™, Patrick Hubbard on January 24th - GMT (UTC+0): 10:00 a.m. to 11:00 a.m. There's still time to RSVP.

Home > Success Center > Network Performance Monitor (NPM) > Time outs when clicking Configure this resource in the Custom Object Resource window

Time outs when clicking Configure this resource in the Custom Object Resource window

Updated February 24, 2017


Timeouts occur when editing a Custom Object Resource using the Configure this resource button and any of its subsequent options such as Choose an Object Type, Selecting an object (such as a group, etc.).



The following error is displayed:

Unexpected Website Error

Request timed out.


NPM versions 12.01 or later



Extend timeout for edit page: 

1. Create a backup the web.config file within the website install folder. Usually this is found     in: C:\inetpub\Solarwinds\.
 2. Edit the web.config file and scroll down to the following block which already exists:

    <location path="Orion/Admin/Accounts/EditAccount.aspx">
          <httpRuntime maxRequestLength="16096" executionTimeout="600" />


 3. Add the following underneath the above:

    <location path="Orion/NetPerfMon/Resources/EditCustomObjectResource.aspx">
          <httpRuntime maxRequestLength="16096" executionTimeout="600" />


  4. Run an iisreset via the Command Prompt as administrator.




Disable the pre-compiled website which should improve performance of this page: 

1. Find the ConfigurationWizard.exe.config file within the program install folder usually c:\Program Files (x86)\SolarWinds\Orion.

2. Edit this file and change this setting value from to: 
<add key="PrecompiledWebsiteDisabled" value="false" />
 <add key="PrecompiledWebsiteDisabled" value="true" />

3. Run the configuration and re-configure website only. Note that re-configuring a website will revert changes within the web.config that was done before.




Last modified