AX2012 freezes when booking sales documents

Hi!

We have a problem with AX2012. A client of ours makes a lot of sales documents (confirmations, picklists, invoices). Sometimes their AX freezes when they make a new booking. For example: They make a new wmspicklist, when they click OK the screen freezes. After 5 minutes (sometimes more) AX is active again and the document appears on the screen and the printer prints the document. This ‘freeze’ happens like 1 or 2 times a day, the rest of the day the system works fine.

Also when creating contactpersons for vendors or customers, the systems freezes sometimes.

I tried to look on the server for any error messages but I can’t find any that are relative to this issue. So… I don’t know where to look to solve this issue.

Any idea’s ?

Thanks in advance

Can you check whether the process isn’t waiting for a resource in database? I would be especially suspicious about inventory tables, because some of them use pessimistic locking.

I can’t tell. AX is freezing and every further action will cause AX to close/crash.

I’m not a system administrator but can you tell me how to look to see if its waiting for a resource?

You’ll likely need somebody familiar with SQL Server. Look at The DBA as Detective: Troubleshooting Locking and Blocking, for example, to get some idea.

Nevertheless you didn’t mention any crashing before (on the contrary, you wrote that “AX is active again”). AX shouldn’t crash if it’s merely waiting for something in database. It’s not clear whether you’re dealing with one problem with different results or two separate problems.

Also, it’s technically possible to analyze a crash log and see what was happening. You would need, again, somebody experienced with that (possibly Microsoft support staff).

Well with crash I mean that the info box “Microsoft Dynamics Axapta 2012 does not respond, close?” appears. This appears when AX freezes and you decide to click a lot. If you do nothing and wait a few minutes, then AX comes back active again,

Aha, I’ve got it now. Thanks for your explanation.