Error with AX client on local machine

(1) Share

Report

Posted on by CU06111021-0

Am having this error “Microsoft Dynamics AX client has stopped working” on the local machines of 4 users but work well on the AOS. please any one can help!

Categories:

Microsoft Dynamics AX

All responses (3)

Answers (0)

Anton Venter 18,788 Super User 2024 Season 2 on at

Like (0)

Report
Error with AX client on local machine

Taking a wild guess here, was a new customisation deployed lately by any chance? Have tried to clear the local object caches (delete *.auc files)?

https://community.dynamics.com/blogs/post/?postid=f4a5aa01-8e07-4409-8c07-f2c4406329a3

Close the user’s client.

Open explorer, type %Appdata%.

Delete the all files ending with .auc.

Open the client.
CU06111021-0 6 on at

Like (0)

Report

Error with AX client on local machine

Here is the event viewer details:

Faulting application name: Ax32.exe, version: 6.3.164.0, time stamp: 0x533f488f
Faulting module name: KERNELBASE.dll, version: 10.0.18362.1237, time stamp: 0x7044674f
Exception code: 0x00000721
Fault offset: 0x001146d2
Faulting process id: 0x2588
Faulting application start time: 0x01db303f4b157c66
Faulting application path: C:\Program Files (x86)\Microsoft Dynamics AX\60\Client\Bin\Ax32.exe
Faulting module path: C:\WINDOWS\System32\KERNELBASE.dll
Report Id: 925dd1c9-6882-4745-b201-bf862ee77198
Faulting package full name:
Faulting package-relative application ID:
Martin Dráb 230,392 Most Valuable Professional on at

Like (0)

Report

Error with AX client on local machine

I already replied in the DUG forum. But as the question is duplicated here, let me duplicate my reply too:

Check out event logs; you may be able to find more details there.

Also, give us more context. Did it work before? If so, what has changed?

You said it works on AOS, but not whether you’re using the same configuration. If you do, you know that the AX client configuration is correct and the problem lies somewhere else (e.g. in firewall rules), but if you’re using different configurations, it may simply mean that the config you’re using on local machines is incorrect and it should match the one you’re using on the AOS.