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)

Workflow message processing job stuck

(0) ShareShare
ReportReport
Posted on by 1,229

I have a client (AX 2012 CU7) that has a re-occurring (not terribly frequent) issue of the Workflow message processing job get's stuck at 50% executing.  My solution is to restart the AOS but since this is a production system (with only one AOS) that is not the most fun thing to do.  Anyone got any ideas?  I saw a post about trying to find the "SPID" in SQL (I think that is what it was called) and killing it?  I have no clue on how to find the "SPID".  Also, I think that it is also possible to go into the BATCH and BATCHJOB tables and changing the STATUS of the job there to 0?  Can this be done without stopping the AOS? 

*This post is locked for comments

I have the same question (0)
  • Suggested answer
    fatihgork Profile Picture
    3,817 on at

    Hello,

    To cancel a running job, we are supposed to change its status to Cancelling, from batch jobs form.

    Have you already set up alert clean up batch?

    I have experienced that issue at change based alerts batch. Clearing the EventCUD was the solution for me. After clearing the EventCUD table, we also set the batch that clears alerts and never experienced that problem again.

  • ford_sopris Profile Picture
    1,229 on at

    Yeah, I set it to Cancelling but it got stuck there.  On the alerts side, I'm curious.  I just noticed that there are over 1.4 MILLION alerts currently on my clients system.  Were you saying that something to do with alerts caused your stuck batch issue?  I just looked in our clients EventCUD table and there was nothing there?  I'll have to look into setting up a batch job to purge the 1.4 million alerts from time time to time (regardless -- seems like 1.4 million is excessive).

  • Verified answer
    fatihgork Profile Picture
    3,817 on at

    Hello,

    When I experienced this issue, the record amount in EventCUD table was huge.

    First tried to clean the notifications with batch, it also got stuck.

    Then we noticed the EventCUD table, cleaned it and then ran the alert clean up batch, it went through,

    Then we set alert clean up batch's recurrence to one month.

    And never experienced that issue again. Currently we have more than 400 active users.

    I hope this will help you to solve that issue.

    Have you tried to delete and recreate your workflow batch jobs already?

  • Suggested answer
    syed baber Profile Picture
    11,633 on at

    Hi Ford,

    Please follow the below link which explains how to find the blocking user session id from SQL server:

    db-it.dk/.../How-to-Show-Blocking-users-for-Dynamics-AX-2012.pdf

    You need to make some changes in the registery, restart AOS server and then you can read the context information to get all the details you want.

    Please verify and let me know if you have further queries.

    Thanks,

    Baber.

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
Martin Dráb Profile Picture

Martin Dráb 4 Most Valuable Professional

#1
Priya_K Profile Picture

Priya_K 4

#3
MyDynamicsNAV Profile Picture

MyDynamicsNAV 2

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans