Faulting Application

Sally Jaber 0

Faulting application name: Ax32Serv.exe, version: 6.3.5000.138, time stamp: 0x582a60f5 Faulting module name: sqlncli11.dll, version: 2011.110.2100.60, time stamp: 0x4f36511a Exception code: 0xc00000fd Fault offset: 0x00000000000b1619 Faulting process id: 0x1880 Faulting application start time: 0x01db0f3f61605724 Faulting application path: C:\Program Files\Microsoft Dynamics AX\60\Server\MicrosoftDynamicsAX\Bin\Ax32Serv.exe Faulting module path: C:\Windows\SYSTEM32\sqlncli11.dll Report Id: 3bcafbb2-7b45-11ef-80f2-00155d205902 Faulting package full name: Faulting package-relative application ID:

I have SQL version 12

Erland Sommarskog 112.5K Reputation points MVP

2024-09-28T16:03:15.9533333+00:00

You had tagged this question SQL Server, which I have changed to Not Monitored. While this crash occurs in SQL Server Native Client 11, there is not much we can do from the SQL Server side of things. Keep in mind that even if the crash occurs in sqlncli11.dll, it may be due to another DLL that has clobbered common memory.

A better place to ask would be in a Dynamics forum, but Dynamics does not seem to be covered by Microsoft Q&A. I would not expect that you will get much response there - unless there happens to be someone else who have run into the same and have a resolution.

If this is a recurring issue, I think it is better to open a support case. Since this has to be construed as a bug, such a support case should be without cost for you in the end.

Share via

Faulting Application

Your answer