Skip to main content

Transaction was deadlocked on lock resources with another process

Updated over 3 weeks ago

This is likely due to environmental issues on the SQL Server Database where there are no enough resources or too many requests accessing the same SQL tables in the database.
​
This then causes SQL to choose a deadlock victim, in which one of the processes are stopped to allow the other to continue.
​
This normally does no lasting damage and simply causes a slight inconvenience for the user as they have to process the action again.

Did this answer your question?