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 :
Dynamics 365 Community / Forums / Microsoft Dynamics AX (Archived) / SysWorkflowMessageQueu...
Microsoft Dynamics AX (Archived)

SysWorkflowMessageQueueManager causing deadlocks

(0) ShareShare
ReportReport
Posted on by Community Member

Version: AX 2012 R3, SQL Server 2012

We have been experiencing an on-going problem with a data deadlock issue. We are using the delivered workflow batch process to post approved timesheets, but numerous timesheets are not being posted due to a data deadlock issue (the TSTimesheetsPostOperation.run batch job). After reviewing the batch job logs, it appears as though the batch job (i.e. sysworkflowmessagequeuemanager) launches several attempts at posting at the same time, and typically it is only the first one launched that is successful. The rest abort because the table ( reference is Accounting Event ) is locked.

This issue has been raised in several blog posts on the Internet, but no solutions have been forthcoming. We did check LCS and implemented a suggestion to increase the recurrence time to 5 minutes – this had no effect ( see Solution 3272330 ).     

Problem sounds very similar to this thread:

https://community.dynamics.com/ax/f/33/t/142522

 

 

*This post is locked for comments

I have the same question (0)
  • André Arnaud de Calavon Profile Picture
    André Arnaud de Cal... 299,509 Super User 2025 Season 2 on at
    RE: SYSWORKFLOWMESSAGEQUEUEMANAGER CAUSING DEADLOCKS

    Hi Budget planning,

    Please don't use capitals in your titles and question details as this is considered as screaming on this forum. I have changed the title for you.

    I have seen the same behavior at a customer, but did not investigate further as it was only a very small portion of the total number of timesheets. When you go to the Unposted timesheets list page, it is possible to post all unposted timesheets at once.

    The recurrence for timesheets has no effect as per approved timesheet a one time batch job is created to post it. When you have e.g. 8 batch server threads, in theory 8 timesheets can be picked up simultaneously for posting. There is indeed a chance that a deadlock might occur due to having timesheets posted together. If it is really a big issue for you, you can create an issue for Microsoft Support.  

  • Mea_ Profile Picture
    Mea_ 60,284 on at
    RE: SYSWORKFLOWMESSAGEQUEUEMANAGER CAUSING DEADLOCKS

    Hi Budget planning,

    Do you have only 1 batch job scheduled for WF ? Because if you have multiple they can deadlock each other. Also you need to check if you don't have any other batch jobs that could lock this table. And you probably saw that MS recommends to increase it further to 10 min and even more if 5 min won't help.

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

News and Announcements

Join experts in person to explore low code and AI agents at the Power Platform Community Conference sponsored by Microsoft

Quick Links

Responsible AI policies

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

Abhilash Warrier – Community Spotlight

We are honored to recognize Abhilash Warrier as our Community Spotlight honoree for…

Congratulations to the September Top 10 Community Leaders!

These are the community rock stars!

Leaderboard > 🔒一 Microsoft Dynamics AX (Archived)

#1
Martin Tocauer Profile Picture

Martin Tocauer 4

#2
Community Member Profile Picture

Community Member 2

#2
Nayyar Siddiqi Profile Picture

Nayyar Siddiqi 2

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans