web
You’re offline. This is a read only version of the page.
close
Skip to main content
Community site session details

Community site session details

Session Id :
Microsoft Dynamics CRM (Archived)

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

(0) ShareShare
ReportReport
Posted on by 297

Hello Everyone!

I am using Workflow Scheduler solution which is available on git hub. In my scenario i want when user go to holiday so he assign his cases to another user and when he come back so his delegated cases again reassign to him. So i created 2 custom activities. In one activity cases are assigned to delegated user successfully when a holiday start date comes and in second activity cases are reassign to primary user when holiday end date comes. Scheduler workflow executes when record of "Recurring Process" entity creates. I am creating 2 records of "Recurring Process" entity. In first record of recurring process creation my cases successfully assigns to delegated user but when creates second record of "Recurring Process" so cases reassign to Primary user from delegated user but it does not work except some records. Because some cases assigned successfully to its primary user but on another cases following error occurred.

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

Kindly Give me suggestion what i do? My activities are correct and i know this problem is occuring due to workflows which are executing parallel. So tell me how to resolve this issue?

*This post is locked for comments

I have the same question (0)
  • Suggested answer
    bac26 Profile Picture
    2,268 on at
    RE: Sql error: 'Transaction (Process ID 184) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction.

    Deadlocks are on the SQL side as it is trying to access something that is already open.    You can work with your SQL DBA to try to fix the deadlocks and he can put in some parameters so it wont' deadlock on the particular table / record.    

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Andrés Arias – Community Spotlight

We are honored to recognize Andrés Arias as our Community Spotlight honoree for…

Leaderboard > 🔒一 Microsoft Dynamics CRM (Archived)

#1
Community Member Profile Picture

Community Member 2

#2
Christoph Pock Profile Picture

Christoph Pock 1

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans