Custom Table Resource using custom SQL query fails with “There was an error while rendering resource with id” for non-administrator accounts in Solarwinds Self-Hosted Platform

6/19/2026 10:01 PM

7/29/2026 2:33 PM

This article discusses an issue where after upgrading to SolarWinds Platform 2026.2.1:

• Widgets that use Custom SQL queries fail only when logged-in as non-administrator account in the Web Console

• The widget will show: an error as shown below:

From OrionWeb log:

ERROR ASP.global_asax - (null)  Application_Error(f49044c38900477e81a2a5a7defbff05)
SolarWinds.Orion.Web.Exceptions.UnauthorizedAccessLocalizedException: You must have the 'Allow Administrator Rights' privilege to perform this operation.
   at AuthorizationChecker.AllowAdmin(String errorMessage)
   at Orion_NetPerfMon_Resources_Reports_ReportTableResourceWrapper.RenderTable(TableConfiguration configuration, DataSource dataSource, TimeFrame timeFrame)
   at Orion_NetPerfMon_Resources_Reports_ReportTableResourceWrapper.OnLoad(EventArgs e)
   at System.Web.UI.Control.LoadRecursive()
   at System.Web.UI.Control.LoadRecursive()
   at System.Web.UI.Control.LoadRecursive()
   at System.Web.UI.Control.LoadRecursive()
   at System.Web.UI.Control.LoadRecursive()
   at System.Web.UI.Control.LoadRecursive()
   at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) 

• The same widgets load successfully for administrator accounts.

• The issue affects both local SolarWinds Platform accounts and Active Directory-managed accounts.

This behavior is caused by how security and account limitations are enforced for Custom SQL data sources in these versions: effectively, rendering the Custom SQL widget requires Allow Administrator Rights.

Starting in 2026.2.2 and later versions, the behavior changes:

 

• Viewing existing Legacy Custom Table widgets that use Custom SQL is restored for all users, including non-administrators.
• Account and view limitations are still not applied to Custom SQL data sources, and only administrators can create new Custom SQL widgets or edit the underlying SQL query text.

 

Network Performance Monitor

In 2026.2 and 2026.2.1, an extra security check was added so that Custom SQL data sources only run for administrator accounts. When a non-admin user hits a Legacy Custom Table that uses Custom SQL, this check blocks the query and raises the “Allow Administrator Rights” error.

In 2026.2.2 and later, this check is relaxed for viewing: non-admins can again see data in existing Custom SQL widgets, but Custom SQL still bypasses account/view limitations, and only admins can create or edit the underlying SQL query.

For environments on 2026.2 and 2026.2.1

In these versions, Custom SQL data sources only run for administrator accounts, which causes the error for non-admin users.

Preferred resolution

• Upgrade to 2026.2.2 or later, where viewing existing Custom SQL widgets is restored for all users.

If you cannot upgrade yet:

• Recommended: Convert the affected widget to use an SWQL data source where possible. SWQL-based widgets respect account and view limitations and allow non-admin users to see only the data they are entitled to.
• Temporary workaround: If no SWQL equivalent is available, limit use of the Custom SQL widget to administrator accounts or tightly controlled admin-equivalent roles until you can upgrade. This avoids exposing raw SQL execution to wider audiences.

For environments on 2026.2.2 and later:

a. Existing Legacy Custom Table widgets that use a Custom SQL data source once again show data to all users who can see the view, including non-administrators. 

b.If you need account or view limitations to control what users see, you should convert the widget to use an SWQL-based data source. 

c. Users with Manage view permission can change the widget configuration (for example, title, layout, and visible columns), but the underlying SQL query text remains read-only for them.