Error with AX client on local machine

Finance and Operations/AX
1

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!

2

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.

3

Thank you, Martin, for your response. 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:

4

Are all the clients the same version? As Martin was saying, are you using the same AXC file for the clients that work and for the ones that don’t?

This error could be anything, but the fact that some machines are not working and some are indicates it’s related to the machines.

Here’s what I’d try to troubleshoot more:

  1. Have a user that’s on an affected machine login to a machine that you’ve had success with. If the user is able to do so, it lends more credence to there being an issue with the original machine.
  2. Confirm the configurations that are being used. If the users aren’t using a shared config file, ensure that the configuration in the Microsoft Dynamics AX Configuration app matches between the problem machine and one that’s working.
  3. Check the versions of .Net installed on both machines. If they’re out of sync, try to get them to match and see if the issue is resolved.
  4. Check the most recent Windows updates. If you’re having issues now and weren’t before, a lot of times a Windows Update could be to blame.

Come back with anymore feedback after you’ve tested these things out.