Network Management
"Check for Orphaned Limitations" in SolarWinds Platform Web Console and Active Diagnostics after upgrading to SolarWinds Platform 2025.1 - 2025.2
This article provides information about the "Check for Orphaned Limitations" warning that appears when performing Health Checks in My Deployment > Deployment Health in the Web Console or running Active Diagnostics after upgrading to SolarWinds Platform 2025.1 - 2025.2
First published date
Last published date
Overview
After upgrading from SolarWinds Platform 2025.1, 2025.1.1 and 2025.2, users may see the following error message when performing Health Checks or running Active Diagnostics:
Error Message:
"Check for orphaned limitations" with the following description:
Found orphaned Limitations:
Limitation type : "Single Database Instance", table [Orion.DPA.DatabaseInstance], field [GlobalDatabaseInstanceID];
Limitation type : "Group of Database Instances", table [Orion.DPA.DatabaseInstance], field [GlobalDatabaseInstanceID];
Limitation type : "Database Instance Name Pattern", table [Orion.DPA.DatabaseInstance], field [Name];
Limitation type : "Single Transaction", table [Orion.SEUM.Transactions], field [TransactionId];
Limitation type : "Group of Transactions", table [Orion.SEUM.Transactions], field [TransactionId];
Limitation type : "Transaction Name Pattern", table [Orion.SEUM.Transactions], field [Name];
Limitation type : "Single Player Location", table [Orion.SEUM.Agents], field [AgentId];
Limitation type : "Group of Player Locations", table [Orion.SEUM.Agents], field [AgentId];
Limitation type : "Player Location Name Pattern", table [Orion.SEUM.Agents], field [Name];
Limitation type : "Group of Network Service Assurance Operations", table [Orion.IpSla.Operations], field [OperationInstanceID];
Limitation type : "Group of CCM SIP Trunks", table [Orion.IpSla.CCMSipTrunk], field [SipTrunkId];
This issue persists even after following the KB article. Troubleshoot orphaned limitations in SolarWinds Platform products and run database maintenance.
Product section
Cause
The issue occurs because the Active Diagnostics test for orphaned limitations does not correctly account for the installed licenses.
The check may reference database tables related to unlicensed modules (e.g., WPM/SEUM) and falsely report orphaned limitations.
Resolution
This issue is fixed in SolarWinds Platform 2025.4 or later. Consider upgrading your environment. If you can't upgrade, use the workaround below.
Users can silence the check in My Deployment > Deployment Health as a workaround to prevent the warning from appearing.