Network Management

Transaction was Deadlocked in the SolarWinds Platform Database

This article describes the issue that occurs when SQL Deadlock transaction error is repeated in a SolarWinds Service log and some ways to address this.

First published date

10/25/2018 8:38 PM

Last published date

9/4/2025 8:07 PM

Overview

A deadlock occurs when two or more SQL  tasks permanently block each other by each task having a lock on a resource which the other tasks are trying to lock. For example:

For more info see: Microsoft Docs Deadlocking

You will see an error similar to the following, this can occur in any log:

System.Data.SqlClient.SqlException (0x80131904): Transaction (Process ID 77) was deadlocked on lock | communication buffer resources with another process and has been chosen as the deadlock victim. Rerun the transaction.

  • System.Data.SqlClient.SqlException indicates that this error occurred in SQL
     
  • The Inner Exception has a ProcessID (Process ID 77). The Process ID will correspond to a SQL SPID which can be tracked in SQL Activity Monitor

Product section

Network Performance Monitor

Cause

Two or more SQL  tasks permanently block each other by each task having a lock on a resource which the other tasks are accessing/using.

 

Resolution

    1. The occasional deadlock error can be ignored as the query will re-execute, however, if you see repeated deadlocks then you may have performance issues.
    2. Check for SQL Performance issues: SQL Server - Performance optimization and best practices.
    3. If this is occurring in a Web Resource or Report try to limit the amount of data being pulled.
    4. Check your current Orion version. Old versions might be subject to bugs that end up causing deadlocks