Tools

ETS for the Web tools throw an exception and show no data (405 Method Not Allowed)

Tools in ETS for the Web, like CPU Monitor and Interface Monitor, don't load any data and display an error: ERROR SolarWinds.Toolset.BusinessLayer.ResultNotification.ResultNotificationProxy - Error occured during remote service call System.ServiceModel.ProtocolException: The remote server returned an unexpected response: (405) Method Not Allowed.

First published date

10/26/2026 1:25 PM

Last published date

10/26/2026 1:29 PM

Overview

After upgrading NPM, the CPU and Interfaces tools in ETS for the Web stopped showing any data. Clicking the "+" icon to expand a node and list interfaces does nothing — no error message, no data, no response.

 

Common symptoms:

 

* CPU Monitor, Interface Monitor, or other ETS for the Web tools return no results.

* Expanding a node to pick interfaces shows an empty list.

* The web page itself doesn't throw a visible error.

* The `Toolset.BusinessLayer.log` file logs a 405 error coming from `ResultNotificationProxy`.

* This tends to show up after an NPM or SolarWinds Platform upgrade, or after the web console URL changes.

 

Product section

Engineers Toolset

Cause

The Toolset service sends tool results back to the web interface using a setting called `CustomBaseServiceUrl`. This setting lives in the Toolset's `web.config` file.

 

If that URL doesn't match the real address of your SolarWinds Platform web console — wrong protocol (`http` vs `https`), wrong port, or just an outdated address — the request lands somewhere it shouldn't. The web server on the other end rejects it with a 405 response instead of accepting it. That's why the tool looks like it's doing nothing: the request goes out, gets rejected, and nothing comes back.

Resolution

1. On the SolarWinds Platform server, back up this file first:

   `C:\Program Files\SolarWinds\Orion\Web\Orion\Toolset\web.config`

2. Open the file with administrator rights.

3. Find the `CustomBaseServiceUrl` key.

4. Make sure the value matches the exact URL you use to open the SolarWinds Platform web console — same protocol (`http` or `https`), same host, same port. It should look like this:

 

 

 

5. Save the file.

6. Restart all SolarWinds services in the SolarWinds Platform Service Manager.

7. Open ETS for the Web again and test Interface Monitor by picking one interface and running it.

 

NOTE: If you're running an HA setup, disable the HA pools before making this change. Re-enable them once you're done and confirmed it's working.