Node Dependencies widget shows “Server error: There was an error processing the request” due to invalid dependency entry in the SolarWinds Platform

2/24/2026 8:02 PM

2/24/2026 8:02 PM

This article covers a case where the Node Dependencies widget on the Node Details page shows:

Server error: There was an error processing the request

while Manage Dependencies still works and Intelligent Maps may also be impacted. The root cause is a corrupt/invalid dependency entry with an empty NetObject prefix, causing the Node Dependencies tree to fail when it tries to render.

Network Performance Monitor

A dependency entry with an empty NetObjectId / prefix exists in the database. When the Node Dependencies widget tries to:

1. Build the tree (DependenciesTree.BuildTree), and

2. Resolve each netobject via NetObjectFactory,

it encounters a dependency whose NetObjectId is "" (empty string). Because there is no valid prefix (N:, I:, V:, etc.), NetObjectFactory throws:

• SolarWinds.Orion.Web.NetObjectFactory+NetObjectFactoryException: Unknown net object prefix: ""

This unhandled exception bubbles up and is rendered in the UI as:

Server error: There was an error processing the request

In this case, the invalid entry was part of auto‑generated dependencies (Auto Dependency based on Topology). Toggling Auto Dependencies forced a full recalculation and eliminated the corrupt entry.

Step 1 – Confirm the specific error in OrionWeb.log

1. Turn OrionWeb.log to DEBUG with Log Adjuster (if more detail is needed).

2. Reproduce the error on an affected node.

3. In OrionWeb.log at C:\ProgramData\SolarWinds\Logs\Orion, confirm:

   • DependenciesTree + Unknown net object prefix: "" as shown above.

If confirmed, proceed.

---

Step 2 – Toggle Auto Dependencies (Primary Fix)

This is the safe, preferred first fix when the bad entry comes from auto dependencies.

1. In the web console, go to:
   Settings → All Settings → Polling Settings.

2. Find the Auto Dependencies setting (typically a checkbox named “Enable Auto Dependencies”).

3. Turn Auto Dependencies OFF:

   • Uncheck the box and Submit.

   • Wait a few minutes to allow the system to remove existing auto‑managed entries.

4. Turn Auto Dependencies ON again:

   • Re‑check Enable Auto Dependencies and Submit.

   • Optionally use Manage Nodes → More actions → Update Topology to refresh topology for relevant nodes.

5. After 5–15 minutes (or one full topology/auto‑dependency cycle):

   • Reopen Node Details → Node Dependencies on one of the previously failing nodes.

   • Confirm the widget now loads and shows the dependency tree without the server error.

This step alone may resolve the Node Dependencies server error and no SQL changes are required.

---

Step 3 – (Optional Advanced) Rebuild Dependency & Group Snapshots via SQL

Use only if:

• Toggling Auto Dependencies does not resolve the error, and

• Logs still show Unknown net object prefix: "" for DependenciesTree, or

• You suspect broader group/dependency snapshot corruption.

Pre‑requisites:

• Your DBA takes a full backup of the SolarWinds Platform database.

• Schedule a short maintenance window (groups/dependencies will recalculate).

A. Stop services on all pollers

On every polling engine (main + APEs):

Stop:

• SolarWinds Information Service V3

• SolarWinds Business Layer Host

• SolarWinds JobEngineV2

• SolarWinds Collector Service (if present)

B. Run SQL against the SolarWinds Platform DB

In the SolarWinds Platform database (e.g. SolarWindsOrion), run:

DELETE FROM [dbo].[ContainerMemberSnapshots];
DELETE FROM [dbo].[LimitationSnapshots];

C. Start services

Start the same services on all pollers:

• SolarWinds Information Service V3

• SolarWinds Business Layer Host

• SolarWinds JobEngineV2

• SolarWinds Collector Service (if present)

Wait 5–15 minutes for groups and dependencies to rebuild.

D. Re-test

• Open Node Details → Node Dependencies for the previously failing nodes.

• Confirm the widget no longer shows the server error.