Observability

Error Rendering Last XX Audit Events Widget After SolarWinds Platform 2025.4.x Upgrade

This article provides information about an issue where the Last XX Audit Events widget fails to load after upgrading the SolarWinds Platform to version 2025.4. Affected environments may see widget errors or unexpected rendering failures. This article explains the cause and provides available workarounds.

First published date

12/2/2025 12:21 AM

Last published date

3/4/2026 3:28 PM

Overview

After upgrading the SolarWinds Platform to 2025.4, users may encounter issues when viewing the Last XX Audit Events widget on Node Details pages. The widget may load for some nodes but fail for others, especially when attempting to display older audit events created before the upgrade.

Common Symptoms

  • The widget displays an error similar to:
    “There was an error rendering: Last XX Audit Events”
  • Editing the widget to increase the number of displayed events or extend the time range causes the widget to fail.
  • Recently generated audit events load correctly, but older audit events (created before the upgrade) fail.
  • Removing and re-adding the widget may temporarily work, but editing any filter/settings causes the error to return.
  • The Message Center still displays all audit events without issue.

Example Error in Logs

Users may find entries in Core.BusinessLayer.log in C:\ProgramData\SolarWinds\Logs\Orion similar to the following:

 

ERROR SolarWinds.Orion.Core.Common.CoreErrorHandler - (null) Error occurred on Business Layer call.
Type: System.Collections.Generic.KeyNotFoundException
Message: 'The given key was not present in the dictionary.'
TargetSite: TValue get_Item(TKey key)
at SolarWinds.Orion.Core.Auditing.AlertSuppression.AlertSuppressionAdded.GetHTMLMessage(...)
at SolarWinds.Orion.Core.BusinessLayer.CoreBusinessLayerService.GetAuditingTable(...)

Product section

Hybrid Cloud Observability

Cause

This issue occurs due to missing audit argument entries in the AuditingArguments table for specific maintenance-related audit events generated before the upgrade.

 

When the widget attempts to process these older events, it expects a "Reason" argument that is missing, leading to a KeyNotFoundException.

Resolution

This issue is fixed in SolarWinds Platform 2026.1. Consider upgrading your environment. If you can't upgrade, use the workarounds below.

 

Workaround 1 - Insert Missing Audit Arguments (SQL Script)

This workaround adds the missing "Reason" argument to affected audit events so the widget can load them correctly.

 

Important:

Before executing any SQL changes, create a full backup of the SolarWinds Platform database.

Note: Table may be very large, so script execution may take time.

 

You may run the script using either:

  • SolarWinds Database Manager, or
  • SQL Server Management Studio (SSMS)

 

-- 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.

INSERT INTO AuditingArguments
SELECT ae.AuditEventID, 'Reason' AS ArgsKey, '' AS ArgsValue
FROM [dbo].[AuditingEvents] ae
INNER JOIN [dbo].[AuditingActionTypes] aat
  ON ae.ActionTypeID = aat.ActionTypeID
     AND aat.ActionType IN       ('Orion.AlertSuppressionAdded','Orion.AlertSuppressionChanged','Orion.EntityUnmanaged')
LEFT JOIN [dbo].[AuditingArguments] aa
  ON aa.AuditEventID = ae.AuditEventID
     AND aa.ArgsKey = 'Reason'
WHERE aa.ArgsKey IS NULL

 

Workaround 2 - Disable Specific Audit Event Types in Widget Settings

If the SQL option is not preferred, the widget can be adjusted to exclude maintenance audit event types that trigger the error.

Steps:

  1. Go to the Last XX Audit Events widget.
  2. Select Edit.
  3. Uncheck the following audit types:
    • Alerts muted
    • Schedule for muting alerts changed
    • Entity unmanaged
  4. Click Submit.

Note:

This workaround prevents the error but also hides these event types from the widget.