[Richard Wu]

Scoured the web for a solution for users that are complaining that their AX 2012 R3 would take too long sometimes to respond when they do a task (click on a menu link, search for a customer, add a sales line item, etc.).  This occurred all of a sudden and seems to continue.  This delay causes a “Microsoft Dynamics AX Processing” notification balloon pops up, is intermittent which lasts typically less than a minute.  Then the next tasks go quickly.  The problem sometimes gets worse in that every single action takes that minute to resolve.  So adding 10 sales lines takes 10 minutes (not good).  The other problem is that everyone on the network will “hang” as well.

So, what causes the entire application for everyone to lock?  Is there an Event on the server (SQL / AOS) to look for?  We’ve looked at antivirus, the max DOP is set to “1” on the SQL server.  The server has loads of memory (20+ GB).  Client computers are also above min recommendations (though since all client computers seem to lock at the same time and even the server, it doesn’t seem like a client-side issue).

——————————
Richard Wu
Bicon, LLC
Boston MA
——————————

[André Arnaud de Calavon]

Hi Richard,

When there is a freeze, you can check the SQL activity monitor to see if there are blocking statements. If this does not give enough hints, you have to do more extensive monitoring: https://docs.microsoft.com/en-us/dynamicsax-2012/appuser-itpro/tools-for-monitoring-performance

I have seen this type of issues due to several reasons. Some are:
– Number sequence cleanup for continuous number sequences is set to automatically. Can be set to manual and use a batch job for the cleanup.
– Customizations
– Anti virus on the client, but also a scan on the AOS
– Heavy tasks are set to run during business hours (or client call or via batch job)

——————————
kind regards,

André Arnaud de Calavon
Product manager, Microsoft MVP – Microsoft Dynamics Business Solutions
——————————
——————————————-

[Richard Wu]

Thank you André.  We think it might be due to some snapshots that are being made that the folks just discovered could have been the potential change that was making some .vhdx files that aren’t being merged.  Still not exactly sure until the files are merged and the problem doesn’t recur to say that was the root cause.  We don’t have any automatic number sequence cleanup or customizations (during that time).  We don’t have any tasks that were different than before.  I’d like to blame the antivirus, but even running it from the server still was slow and made everyone freeze.  Hopefully we’ll get these snapshots fixed and these strangling .vhdx files don’t get re-created.

——————————
Richard Wu
Bicon, LLC
Boston MA
——————————
——————————————-