Network Management

Database Maintenance fails to complete in the SolarWinds Platform when the Transaction log is full

This article describes where the Database Maintenance takes too long then fails to complete in the SolarrWinds Platform.

First published date

9/19/2019 9:24 AM

Last published date

3/31/2026 4:57 PM

Overview

Check the following logfile C:\Programdata\Solarwinds\Logs\Orion\SWDebugMaintenance.log

Database Maintenance is failing due to error:

Failed to execute procedure: dbm_SyslogMessages_DeleteStale
System.Data.SqlClient.SqlException (0x80131904): The transaction log for database 'SolarWindsOrion' is full due to 'ACTIVE_TRANSACTION'.

Product section

Orion Platform

Cause

This can happen when too many Syslogs are forwarded to the SolarWinds Platform pollers.
The stored procedure to remove Syslogs based on retention settings is unable to complete.

Resolution

1. Review SWDebugMaintenance.log to determine at which portion of the maintenance the failure occurred and why it took time.

2. The error below indicates that maintenance failed to complete a stored procedure as the transaction log is full.

Failed to execute procedure: dbm_SyslogMessages_DeleteStale
System.Data.SqlClient.SqlException (0x80131904): The transaction log for database 'SolarWindsOrion' is full due to 'ACTIVE_TRANSACTION'.

The following articles might help:

For the transaction log issue:
- Database Manager: The transaction log for database NPM is full

For the Syslog:
- SQL reports the NPM database is currently out of space

It would also be a good idea to ensure that they are following our SQL Recommendations as closely as possible.
- SQL Server configuration best practices for SolarWinds Platform products

Disclaimer: Please note, any content posted herein is provided as a suggestion or recommendation to you for your internal use. This is not part of the SolarWinds software or documentation that you purchased from SolarWinds, and the information set forth herein may come from third parties. Your organization should internally review and assess to what extent, if any, such custom scripts or recommendations will be incorporated into your environment. You elect to use third-party content at your own risk, and you will be solely responsible for the incorporation of the same if any.