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


It is uncertain how the deadlocks occur, but it may be application related or due to too many processes running concurrently.  To avoid this, all the lookup tables are scheduled to execute every hour.  The specific deadlock error message that can occur is as follows:

 

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

 

When an agent becomes chosen as a deadlock victim, it will go into retry mode.  Once it is in this state, it normally does not start again on its own.   To correct this error, follow the following steps:

 

  1. Stop all agents that have been chosen as a deadlock victim.
  2. Start each agent one by one.  Be sure the agent has started before moving on to the next stopped agent.
Advertisements
This entry was posted in Replication. Bookmark the permalink.

One Response to Transaction was deadlocked on lock resources : Transaction (Process ID #) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction

  1. Shannan says:

    I read a lot of interesting content here. Probably you
    spend a lot of time writing, i know how to save you a lot of time,
    there is an online tool that creates readable, google friendly articles in seconds,
    just search in google – laranitas free content source

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s