Observability

Node child status participation misconfiguration causes Vital Stats graphs to keep loading in SolarWinds Platform

This article describes how to resolve an issue where Vital Stats graphs on the Node Details page remain in a continuous loading state or show no data, even though node polling and system resources appear healthy. The problem is caused by a misconfiguration of node child status participation in the database and is resolved by correcting the NodeChildStatusParticipation table and restarting SolarWinds services.

First published date

2/12/2026 5:35 PM

Last published date

2/12/2026 5:35 PM

Overview

Symptoms

You may observe one or more of the following:

  • On the Node Details page, the Summary view loads as expected, but the Vital Stats tab keeps spinning or fails to render data.

  • The issue can recur periodically (for example, every few weeks).

  • Running the Configuration Wizard restores Vital Stats temporarily, but the issue returns after some time.

  • General polling and other widgets appear healthy.

Product section

SolarWinds Observability

Cause

The issue occurs when child participation for certain entities (specifically Orion.NPM.Interfaces) is not correctly enabled in the NodeChildStatusParticipation table in the SolarWinds Platform database.

When Vital Stats is loaded, the SolarWinds Platform calculates node child status by combining node, application, and interface data. If interface data exists but the corresponding participation flags are disabled or inconsistent, NodeChildStatusDAL throws an exception:

  • Data for Orion.NPM.Interfaces is present,

  • But it is not marked as part of node participation,

  • Causing the child status computation to fail and Vital Stats to stay in a loading state.

Running the Configuration Wizard can temporarily correct the configuration, but if the underlying participation flags remain misconfigured, the issue can recur after some time.

Resolution

Important

  • Always take a full backup of the SolarWinds Platform database before making any direct SQL changes.

  • Perform these steps during a maintenance window as they require SolarWinds services to be stopped.

If you are using High Availability (HA), coordinate carefully and plan for temporary downtime.

Step 1: Confirm the error in the logs

  1. On the main polling engine, open:

    • C:\ProgramData\SolarWinds\Logs\Orion\OrionWeb.log

  2. Reproduce the issue by opening the Node Details page and then the Vital Stats tab for an affected node.

  3. Confirm you see errors like:

    Unexpected error while processing node child status data
    System.InvalidOperationException: Data for Entity Type 'Orion.NPM.Interfaces' was found, yet not part of Node Participation.
    

If this error is present, proceed to the next steps.

Step 2: Prepare the environment

    1. Ensure you have a recent backup of the SolarWinds Platform database.

    2. If High Availability is enabled:

      • Temporarily disable HA globally to avoid automatic failover while services are stopped.

    3. On the main active polling engine, stop all SolarWinds services:

      • Open SolarWinds Platform Service Manager (or Services.msc).

    4. Stop all SolarWinds services.

Step 3: Correct node child status participation in the database

Run the following SQL script against the Orion database (for example, in SQL Server Management Studio):

-- Disclaimer: Scripts are not supported under any SolarWinds support program or service.
-- Scripts are provided AS IS without warranty of any kind.
-- SolarWinds further disclaims all warranties including, without limitation, any implied warranties
-- of merchantability or of fitness for a particular purpose.
-- The risk arising out of the use or performance of the scripts and documentation stays with you.
-- In no event shall SolarWinds or anyone else involved in the creation, production, or delivery of the
-- scripts be liable for any damages whatsoever (including, without limitation, damages for loss of
-- business profits, business interruption, loss of business information, or other pecuniary loss)
-- arising out of the use of or inability to use the scripts or documentation.

UPDATE [dbo].[NodeChildStatusParticipation]
SET Enabled = 1,
    Installed = 1,
    Excluded = 0;

This statement ensures that all defined child entities (including Orion.NPM.Interfaces) are:

  • Enabled for participation in node child status,

  • Marked as Installed,

  • Not Excluded from the calculation.

Step 4: Restart SolarWinds services

  1. On the main polling engine, start all SolarWinds services again:

    • Use SolarWinds Platform Service Manager to start all services.

  2. If you temporarily disabled High Availability:

    • Re‑enable HA globally after services are up and the environment is stable.

Step 5: Validate Vital Stats

  1. Log in to the SolarWinds web console.

  2. Open an affected node’s Node Details page.

  3. Click the Vital Stats tab.

  4. Confirm that:

    • The page loads successfully without errors,

    • Metrics are displayed as expected,

    • The issue does not recur after normal operation.

If the issue returns or the error persists in the logs, collect updated diagnostics (including OrionWeb.log, SWIS logs, and HAR capture) and contact SolarWinds Support for further analysis, referencing that NodeChildStatusParticipation has already been corrected.