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

Notifications

Announcements

No record found.

Community site session details

Community site session details

Session Id :
Microsoft Dynamics AX (Archived)

Instance of AX got frozen frequently by End User while working with Production posting.

(0) ShareShare
ReportReport
Posted on by 200

This is happened in start button or reported as finished which belongs to Update of Batch Order of Production Area. It also happens while posting from picking List or Route Card and that belongs to Journal of Batch Order of Production. Towards having the cause of being occurred, we went to Database. On Activity Monitor > Processes, We found an update lock and its wait type is “lck_m_u”.  Having it "Blocked By" value which to be used in getting the exact Session ID. And if we use "kill the process” having right click on that identified session, it would become workable again. When it gets frozen, all the end users become frozen (screen non-workable mode). We hope you in having full co-operation in solving as quickly as possible. Thanks in Advance.

*This post is locked for comments

I have the same question (0)
  • Community Member Profile Picture
    on at

    Hi

    Did you ever find an answer to this? We are having the same problem and struggling.

  • Alex Voytsekhovskiy Profile Picture
    on at

    The same problem! Suspended Select on WrkCtrSchedulerLock in AX 2012

  • Mohammad Adnan Profile Picture
    200 on at

    YEs we did and we had to do lot of tunning at the SQL database level. One of my AX support Company went thru regorous reseach to fix this issue. If you would liek I can provide their contact information.

  • Alex Voytsekhovskiy Profile Picture
    on at

    Hi Mohammad! What was the main reason of this problem? Thank you.

  • Community Member Profile Picture
    on at

    Did you ever find out the root cause or a fix for this?

  • Community Member Profile Picture
    on at

    We had the same issue, the users seemed to be locked by the WRKCTRSCHEDULERLOCK table, but this functions as designed. That lock is supposed to come, the problem was that the BOMCheck took ages after the lock was set. We have massive BOM and checking a BOM takes a long time. During that time the lock is just waiting to be released until the check is finished.

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…

Neeraj Kumar – Community Spotlight

We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…

Leaderboard > 🔒一 Microsoft Dynamics AX (Archived)

#1
Priya_K Profile Picture

Priya_K 4

#1
Martin Dráb Profile Picture

Martin Dráb 4 Most Valuable Professional

#3
MyDynamicsNAV Profile Picture

MyDynamicsNAV 2

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans