Personalized Community is here!
Quickly customize your community to find the content you seek.
Choose your path Increase your proficiency with the Dynamics 365 applications that you already use and learn more about the apps that interest you. Up your game with a learning path tailored to today's Dynamics 365 masterminds and designed to prepare you for industry-recognized Microsoft certifications.
Visit Microsoft Learn
2020 Release Wave 2Discover the latest updates and new features to Dynamics 365 planned through March 2021.
Release overview guides and videos Release Plan | Preview 2020 Release Wave 2 TimelineWatch the 2020 Release Wave 1 virtual launch event
Ace your Dynamics 365 deployment with packaged services delivered by expert consultants. | Explore service offerings
Connect with the ISV success team on the latest roadmap, developer tool for AppSource certification, and ISV community engagements | ISV self-service portal
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Program | Finance TechTalks | Customer Engagement TechTalks | Upcoming TechTalks
We have a problem in AX 2009 where MRP batch job occasionally gets stuck with Executing status every couple of weeks and doesn't not finish. Normally, it finishes within an hour or so, but when it get stuck, it can hang in that status for the whole day. Then it needs to be canceled and it runs fine the next time. There's no specific pattern to it. Some clean up of the tables related to MRP has been performed. When logging was enabled to see if any particular items are taking longer than normal to process, the job was taking too much time to process a large number of items and had to be canceled. Any suggestions how to troubleshoot this sporadic issue?
Can you tell when you run the MRP? Can you check if there are at that time also other tasks, like maintenance jobs or a backup procedure of the SQL database?
We already checked those and made sure there're minimal to no overlaps between other tasks.
I would suggest to do the the following.
3. If 1 & 2 does not resolve issue, reproduce your issue in dev environment & debug it
I checked SysBreakpoints and SysBreakpointsList tables according to one of the posts and found over a hundred in one and thousands of old records in the other one respectively. These breakpoints are not visible in AOT and are not removed when I try to delete them (CTRL+SHIFT+F9 in AOT). I understand that this is not a good sign that some users likely performed a lot of debugging in PROD. I wonder how this can affect application if debugging is off.
I will continue looking for other potential issues.
How is your progress here? Do you have already some additional insights or do you need more help?
Business Applications communities