Network Management

"RunQuery Failed: Entity Orion.NodesCustomProperties Does Not Contain Requested Property" error in the SolarWinds Platform Web Console

SolarWinds web console pages that reference a Node custom property (Maps, Alert History, Node Details, AppStack, widgets) display "Unexpected Website Error" with the message: "RunQuery failed, check fault information. Entity Orion.NodesCustomProperties does not contain requested property [PropertyName]." The property exists in Manage Custom Properties but SWIS cannot resolve it when queried.

First published date

7/30/2026 8:55 PM

Last published date

7/30/2026 9:26 PM

Overview

Symptoms

  • Navigating to a page or resource that references a specific Node custom property results in "Unexpected Website Error"

  • The custom property is visible and selectable in Settings > All Settings > Manage Custom Properties

  • The error may occur on specific servers (e.g., additional web server via FQDN) while other servers (e.g., MPE via IP) work correctly

  • The error may affect Map interface details, Alert History links, Node Details pages, AppStack Environment, or any widget/resource that queries the custom property

Related Error

  • "Unexpected Website Error"

  • Message: RunQuery failed, check fault information.

  • Entity Orion.NodesCustomProperties does not contain requested property [PropertyName]

  • Entity Orion.NodesCustomProperties does not contain requested property [PropertyName] of navigation property e.CustomProperties

Environment

  • SolarWinds Platform (all versions)

  • Any module referencing Node custom properties (NPM, SAM, NCM, etc.)

Product section

Network Performance Monitor

Cause

The SolarWinds Information Service (SWIS) maintains an in-memory schema cache of all custom properties. This cache can become stale or inconsistent in two scenarios:

  • Scenario A — Property exists but SWIS cache is stale: A custom property was recently created or recreated, but the SWIS instance on a specific server did not receive the schema change notification. The property exists in the database but the SWIS schema cache on that server does not include it.

  • Scenario B — Property no longer exists in the database: A custom property was deleted from the database (manually or via another tool) but is still referenced by Map resources, alert conditions, widget groupings, or view configurations. SWIS cannot resolve a property that no longer has a corresponding database column.

Resolution

Path 1 — If the custom property is still needed (Scenario A)

  1. Identify which server the error occurs on (check FQDN resolution via nslookup if applicable)

  2. On that server, open Services.msc or SolarWinds Service Manager

  3. Restart the SolarWinds Information Service (SWISv3)

  4. Wait 1-2 minutes for the service to fully start and reload the schema

  5. Re-test the affected page — the error should be resolved

If the environment has multiple polling engines or additional web servers, restart the SolarWinds Information Service on each affected server.

Path 2 — If the custom property is no longer needed (Scenario B)

  1. Navigate to Settings > All Settings > Manage Custom Properties

  2. Select the custom property referenced in the error message

  3. Delete the custom property

  4. Re-test the affected page — the error should be resolved

Note: Before deleting, verify the property is not actively used by alerts, reports, or views. Check alert configurations and widget settings for references to the property name.