Faulting application Ax32Serv.exe

(0) Share

Report

Posted on by Luke Brabin

Hi,

We are running Dynamics AX 2009, and we are occasionally/regularly getting an error on any of our 3 AOS servers, with the following details in the event viewer:

Faulting application Ax32Serv.exe, version 5.0.1000.52, time stamp 0x490c68d8, faulting module ntdll.dll, version 6.0.6002.18005, time stamp 0x49e0421d, exception code 0xc0000374, fault offset 0x00000000000aef37, process id 0xec8, application start time 0x01cc21bb0e81adbe.

Whenever this occurs, the AOS server services need to restart and all users are booted out of Dynamics AX. SCOM alerts the administrator to the problem - but we are unsure what is casuing the error. We are not able to reproduce the error manually/on purpose, and we are unsure what is triggering it.

How can we get more information on this error? Are there any other log files we can check? How can we trouble shoot this further?

Any help greatly appreciated.

Many Thanks,

Luke.

*This post is locked for comments

I have the same question (0)

All responses (8)

Answers (0)

Community Member on at

Like (0)

Report

Try this:

blogs.msdn.com/.../what-to-do-if-you-have-a-crash.aspx

Regards,

S.C.GAN

Was this reply helpful? Yes No
Praveen 1,201 on at

Like (0)

Report

Apart from the memory dump for crashes, in these cases, I would try to check the log files thorougly and any logs needs to be seen in all perspectives for eg:- check all logs 30 mins before the crash, if there was any abnormality and a particular session is causing an issue...

Thanks, hope it helps. Please revert back if you did find the root cause.

Was this reply helpful? Yes No
Joris dG 17,775 on at

Like (0)

Report

This types of issues are tough to troubleshoot. From your pasted message I can tell your are not on the latest hotfix rollups. It is always interesting to go through those rollup documentations and see if there are any fixes related to server crashes, which may apply to you and point you in a direction of being able to replicate the issue.

The only server crashes I have had no too long ago were related to using printers on the AOS server, which after a while we were able to replicate, although they were obscure issues. What we did to troubleshoot, was trying to figure out what users were doing when things crashed. We used user logs to find out who was on the system at the time, and called each individual up to ask if they were trying anything in particular. Usually users do not realize they are causing the trouble, however they are angry they are unable to perform a certain task since every time they've tried lately, "the system has been going down". Now, I realize depending on your number of users this may be a daunting task. When you go through the user log, look for patterns, certain users who were always on at the time of the crash, etc.

Was this reply helpful? Yes No
Marilena 230 on at

Like (0)

Report

Hi Luke,

Did you ever figure out what was causing your issue? I am running into a similar error with a client and I am looking for some feedback.

Thanks!

Was this reply helpful? Yes No
640579632b5c4e6780a... 4,730 on at

Like (0)

Report

Is there some schedule program which runs after 30 mins or so . some time anti virus cause this problem.

Was this reply helpful? Yes No
640579632b5c4e6780a... 4,730 on at

Like (0)

Report

What causes this ntdll.dll crash with a faulting module?

In most cases this error results from three reasons:

1) The file is either corrupted/missing.

2) Damaged registry.

3) Conflicts between Windows and other applications.

Was this reply helpful? Yes No
Jake Trenholm on at

Like (0)

Report

Found this via internet research (hi to Joris) looking for some resolution. Also have a MS Ticket open to resolve. Wondering if anyone did have a precise solution by chance? Otherwise, I'll work with MS and post anything we determine.

I've periodically noticed the exact same error (small differences in versions), but relative to Ax32Serv.exe and the NTDLL.DLL. Occurrences about once a month or so, random crash. I now have the "logging" on, to obtain better information upon the next crash, but in the meantime...here's the error I'm getting:

Faulting application name: Ax32Serv.exe, version: 5.0.1500.3260, time stamp: 0x4c485626

Faulting module name: ntdll.dll, version: 6.1.7600.16695, time stamp: 0x4cc7b325

Exception code: 0xc0000005

Fault offset: 0x00000000000515b0

Faulting process id: 0x%9

Faulting application start time: 0x%10

Faulting application path: %11

Faulting module path: %12

Report Id: %13

There is a "similar" KB Article I found (support.microsoft.com/.../2258719), but it's related to Faulting Module = KERNELBASE.DLL instead - but may be a solution.

Was this reply helpful? Yes No
KishorJadhav 162 on at

Like (0)

Report

Hi Jake,

Can you please let me know , how you resolved this issue ?

Was this reply helpful? Yes No