Orphaned Limitations - Limitation types based on missing properties

We have a very strange issue with Limitations. Within the database check all a couple of limitations (Solarwinds default) in the LimitationsType table are wrong according to Orion.

Found orphaned Limitations:
Limitation types based on missing properties:
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 Datastore", table [Orion.VIM.Datastores], field [DataStoreID];
Limitation type : "Group of Datastores", table [Orion.VIM.Datastores], field [DataStoreID];
Limitation type : "Datastore Name Pattern", table [Orion.VIM.Datastores], 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];
Limitation type : "Group of Network Service Assurance Operations", table [Orion.IpSla.Operations], field [OperationInstanceID];

And after inspecting the table in detail, the following row existed twice, only having a different ID.

Limitation type : "Group of Network Service Assurance Operations", table [Orion.IpSla.Operations], field [OperationInstanceID];

This is not fixable by standard limitation creation issues.

How to fix this?

Find more posts tagged with

Accepted answers

All comments

Loop1Cole

Hey,

I reached out to SolarWinds support regarding this, and they provided me with the following:

"Regarding your concern, our developers are aware of the behavior. As of today, no fix is available, and development is still investigating the issue.

Users can silence the check in My Deployment > Deployment Health as a workaround to prevent the warning from appearing."

RAJPAD

Hi Loop1Cole, please provide me with your support case number, so that I can silence my issue as well.

zennifer

I have a bit of a different issue, but similar.

Now that I have upgraded to 2025.x… I wanted to pass the health check! I am down to 2 Warnings. First warning is just a little more work on my part to eliminate SNMPv2 and use only v3.

The other issue which should be resolved is regarding orphaned Limitations:

Found orphaned Limitations:

Limitation types based on missing properties:

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];

What you can do

Delete orphaned limitations from database.

Related KB articles

MT103094

I followed the steps in the KB article, running the following script with database manager (after I backed up the database):

DELETE FROM [Limitations] WHERE [LimitationID] NOT IN

(

SELECT DISTINCT [LimitationID1] AS LimitationID FROM [Accounts] WHERE [LimitationID1] IS NOT NULL

UNION

SELECT DISTINCT [LimitationID2] AS LimitationID FROM [Accounts] WHERE [LimitationID2] IS NOT NULL

UNION

SELECT DISTINCT [LimitationID3] AS LimitationID FROM [Accounts] WHERE [LimitationID3] IS NOT NULL

UNION

SELECT DISTINCT [LimitationID] AS LimitationID FROM [Views] WHERE [LimitationID] IS NOT NULL

)

update [Views] set LimitationID = null

where LimitationID is not null and LimitationID not in

(select l.LimitationID from [Limitations] l)

update [Accounts] set LimitationID1 = null

where LimitationID1 is not null and LimitationID1 not in

(select l.LimitationID from [Limitations] l)

update [Accounts] set LimitationID2 = null

where LimitationID2 is not null and LimitationID2 not in

(select l.LimitationID from [Limitations] l)

update [Accounts] set LimitationID3 = null

where LimitationID3 is not null and LimitationID3 not in

(select l.LimitationID from [Limitations] l)

DELETE l FROM Limitations l

left join LimitationTypes lt on l.LimitationTypeID = lt.LimitationTypeID where lt.[LimitationTypeName] is null

This script, after executed, removed 59 records.

I also ran the following script:

DELETE L FROM Limitations L LEFT JOIN LimitationTypes LT ON L.LimitationTypeID = LT.LimitationTypeID WHERE LT.LimitationTypeName IS NULL;

The script did not find any records.

The database maintenance runs clean and successfully executes all clean up routines to include the orphaned objects.

I would like to think that this is a bug in the code for health check reporting; a false positive? ...... do you think I should log this in a support case as well.

RAJPAD

Hi zen, same issue, upgrade 2025.x, the script did not find any records, so I silenced the issue. there was another thwackster that logged a support ticket and was told to silence this issue.