Submit a ticketCall us

Don’t fall victim to a ransomware attack
Backups are helpful, but sometimes that’s not enough to protect your business against ransomware. At our live webcast we will discuss how to protect against ransomware attacks with SolarWinds® Patch Manager and how to leverage log data to detect ransomware. Register now for our live webcast.

Home > Success Center > Network Performance Monitor (NPM) > Database configuration failed: Error while executing script - Transaction (Process ID number) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction

Database configuration failed: Error while executing script - Transaction (Process ID number) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction

Updated June 7, 2017

Overview

The following error is displayed when running the configuration wizard:

Database configuration failed:

Error while executing script - Transaction (Process ID ###) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction.


The following errors are also found in the ConfigurationWizard.log file:

  • ERROR ConfigurationProgressScene - Error while executing script- Transaction (Process ID ###) was deadlocked on lock resources with another process and has been chosen as the deadlock victim.  Rerun the transaction.
  • INFO OipClient - Tracking event:  ConfigurationWizard - ConfigurationProgressScene - UpdateFailureText - Error while executing script- Transaction (Process ID ###) was deadlocked on lock resources with another process and has been chosen as the deadlock victim.  Rerun the transaction.
  • - False - 0

Environment

ALL NPM versions

Cause 

SQL deadlocks are caused by insufficient resources on the server hosting the SQL database, or insufficient resources allocated to the database instance itself.

See the Deadlocking article for more information regarding SQL deadlocks.

(© 2017 Microsoft Inc., available at http://www.technet.microsoft.com, obtained on June 6, 2017.)

Resolution

Make sure that all unnecessary database instances that run on the SQL Server are taken offline via Microsoft SQL Management Studio. Please take note that this can have a production impact and is only advised if you are able to positively confirm that the database instances running on a shared SQL Server are unnecessary. Consult with your database administrator if there are doubts as to whether a database instance is necessary to be kept online.

See the SQL Server - Performance optimization and best practices article for more information.

 

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.

 

 

Last modified
17:54, 6 Jun 2017

Tags

Classifications

Public