
Hello,
I am running into an issue where one particular store is getting stuck during posting when in batch processing. The issue starting occurring about two weeks ago. The job is able to calculate the statement with no issues, but it is getting stuck somewhere in the posting process. Before that, the job was scheduled to start at 10:20 PM (EST), and would usually run in 20-30 minutes. However, since this issue has occurred, the job will continually run until it is canceled. The longest I let the job run for was 8 hours and it still did not finish. I have tried moving the start time of the job multiple times to see if it would help, but the issue remain.
What I find strange this issue is that when the job is canceled, I can go post the statement manually with no issue, and it will only take a couple of minutes. Originally I thought maybe someone had changed the setup of the store, but I don't see how that would be possible if I'm able to manually post the statement with no issues.
Lastly, the night before this issue started we did have a problem with our batch jobs running long. In addition to that, we have "clean up" jobs that will try to post any statements that failed the first time around. Because of this setup, when this store's statement posting was running long, the clean up job tried to post the same statement before the original posting was finished. I am wondering if this didn't leave some residual data on the DB that is causing the issue when this particular store's statement is trying to post. However, once again I would think this would affect the statement when I try to manually post it, but that doesn't seem to be the case. I should mention, we are using AX 2012, CU 8.
My question is, does any one have an idea on how to go about solving this issue? Also, does someone know, or could point me to an information source regarding when a statement is posting in a job, but then another job tries to post that same statement before the original job is done posting.
-Luke
*This post is locked for comments
I have the same question (0)