web
You’re offline. This is a read only version of the page.
close
Skip to main content

Notifications

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id :
Dynamics 365 Community / Forums / Microsoft Dynamics AX (Archived) / AOS crash
Microsoft Dynamics AX (Archived)

AOS crash

(0) ShareShare
ReportReport
Posted on by Community Member

Hi,

We have crashes on AX 2012 R3 CU10 (service is unexpectedly down) and these logs are dropped in event viewer :

1.

Faulting application name: Ax32Serv.exe, version: 6.3.3000.111, time stamp: 0x565004b8
Faulting module name: KERNELBASE.dll, version: 6.3.9600.17415, time stamp: 0x54505737
Exception code: 0xc0000005
Fault offset: 0x0000000000008b9c
Faulting process id: 0x1d14
Faulting application start time: 0x01d1f6ca807f66fe
Faulting application path: C:\Program Files\Microsoft Dynamics AX\60\Server\ECOMAX63Gate\Bin\Ax32Serv.exe
Faulting module path: C:\Windows\system32\KERNELBASE.dll
Report Id: 7f6efa57-62ce-11e6-80e8-005056ac23bc
Faulting package full name:
Faulting package-relative application ID:

2.

Object Server 01:  Unexpected situation
 More Information: Cursor building error 1

Any help will be appreciated

Thanks

*This post is locked for comments

I have the same question (0)
  • Sohaib Cheema Profile Picture
    Sohaib Cheema 49,438 User Group Leader on at

    Events logs are not useful, in many cases, as those speak very less about insights of AX.

    If you are interested to see why its being crashed, you may collect Crash Dump using either Windows Error Reporting (WER) or by using any tool such as DebugDiag

    Usually I have found Windows Error Reporting (WER) very useful.

    collect crash dump file and then upload it on LCS, it can reveal you the facts about crashing of AOS

  • Vilmos Kintera Profile Picture
    Vilmos Kintera 46,149 on at

    The unexpected situation in most of the cases means there is some problems between the Microsoft SQL Server and the Microsoft Dynamics AX Application Object Servers' communication (i.e. stuck server/client sessions, timeouts).

    What can you see in SQL Server Management Studio if you connect to your SQL Server instance where AX is sitting under the Management > SQL Server logs > Current, which are errors and could be related to your problem?

    Are you experiencing this issue after changing something in the AOS ie. a code release, or it just happens all of a sudden? Do you monitor available disk space, memory and CPU usage on the AOS instances where the crash happens? It could be that you are just out of resources for some reason and then the AX kernel fails to do some operations.

  • Community Member Profile Picture
    Community Member on at

    Dear Sohaib, Thanks.

    I'm going to do this using WER but in windows 2012 R2 there was no key under windows error reporting so I made both of them manually as you see below. Is that Ok? (and BTW, WER service is configured and set to auto start)

    And another question, Do you suggest any method to make an intentional crash to test if these settings are working and dump file is created?

    photo_5F00_2016_2D00_08_2D00_16_5F00_11_2D00_29_2D00_47.jpg

    Oh and does this need a server restart to be applied ?

  • Sohaib Cheema Profile Picture
    Sohaib Cheema 49,438 User Group Leader on at

    1) It is fine to create a custom key, as you need to track AX application.

    2) I don't recommend making intentional crash. Let users use system and next time when they report a crash, you will find one file in folder which you have setup for crash dumps/ you may inform to users that they are going to face another crash or may be few more unless you get actual reason of crash.

    3) yes it needs restart of machine/aos server, after enabling WER Crash dump

  • Community Member Profile Picture
    Community Member on at

    And it happened again ...

    I made the changes to registry but did not restart and no dump file is created in the folder specified in registry. I hope they are finely defined and next time we will have the log. But, there was a log capture session using Microsoft procdump whose generated dump is more than 10GB ! A log analysis tool gave us these results.

    And to add more :

    This is logged just seconds before crash : (System)

    A timeout (30000 milliseconds) was reached while waiting for a transaction response from the AOS60$01 service.

    And in Application :

    The 'user' header cannot be passed into the service.

    The 'user' header cannot be passed into the service.

    The 'user' header cannot be passed into the service.

    and many Error of 180 whose descriptions as you know cannot be found

    Also this is logged every second (displaying in procdump tool) :

    [19:30:15] Exception: E0434352.CLR
    [19:30:15] Exception: E0434352.CLR
    [19:32:16] Exception: E0434352.CLR
    [19:32:16] Exception: E0434352.CLR
    [19:32:16] Exception: E0434352.CLR
    [19:32:18] Exception: E0434352.CLR
    [19:32:18] Exception: E0434352.CLR
    [19:32:18] Exception: E0434352.CLR
    [19:33:47] Exception: E0000000
    [19:45:48] Exception: E0434352.CLR

    1. Does it clear anything ?

    2. Does LCS allow sending log files of such a huge size ?! (Cause we don't know when the crash happens we must constantly run the dump collector behind the scenes and there maybe a long time for the crash to happen so a very large file ...)

    https://1drv.ms/u/s!AmHGMfHihpNGg0v8CdvKfgTRFqYw

    Here is the summary

    Analysis Summary
     
    TypeDescriptionRecommendation
        Notification
    The process Ax32Serv.exe in Ax32Serv.exe_160816_154849.dmp is a 64 bit application. Some of the native (non-.NET) analysis, such as winsock information, may be missing. Further manual inspection of the dump may be required to extract such information.
        Error WARNING - DebugDiag was not able to locate debug symbols for \msvcr100.dll, so the information below may be incomplete.

    In Ax32Serv.exe_160816_154849.dmp the assembly instruction at msvcr100!wcslen+3 in C:\Windows\System32\msvcr100.dll from Microsoft Corporation has caused an access violation exception (0xC0000005) when trying to read from memory location 0x00000000 on thread 136    		 Please follow up with the vendor Microsoft Corporation for C:\Windows\System32\msvcr100.dll
        Warning The following threads in Ax32Serv.exe_160816_154849.dmp are making a call to Sleep API using the .net Library

    ( 76 )

    0.53% of threads blocked (1 threads)

    		 The duration of the Sleep call is unavailable. Please look at the callstack and the code of the function that is calling Sleep to determine the actual time the thread is sleeping.
        Warning The following threads in Ax32Serv.exe_160816_154849.dmp have evidence of previous .net exceptions on the stack

    ( 136 )

    		 Check the Previous .NET Exceptions Report (Exceptions in all .NET Thread Stacks) to view more details of the associated exception
        Information The following threads in Ax32Serv.exe_160816_154849.dmp are waiting in a WaitMultiple

    ( 167 )

    0.53% of threads blocked (1 threads)

    		  
        Information There are 6 modules which are compiled in DEBUG mode. Please check the List of modules compiled in Debug mode to see those modules and recompile them in Release mode  

    Exception Information

    MSVCR100!WCSLEN+3WARNING - DebugDiag was not able to locate debug symbols for \msvcr100.dll, so the information below may be incomplete.

    In Ax32Serv.exe_160816_154849.dmp the assembly instruction at msvcr100!wcslen+3 in C:\Windows\System32\msvcr100.dll from Microsoft Corporation has caused an access violation exception (0xC0000005) when trying to read from memory location 0x00000000 on thread 136

    Module Information
    Image Name: C:\Windows\System32\msvcr100.dll   Symbol Type: Export
    Base address: 0x00000003`00905a4d   Time Stamp: Sat Jun 11 05:24:04 2011
    Checksum: 0x00000000`00000000   Comments:
    COM DLL: False   Company Name: Microsoft Corporation
    ISAPIExtension: False   File Description: Microsoft® C Runtime Library
    ISAPIFilter: False   File Version: 10.00.40219.325
    Managed DLL: False   Internal Name: msvcr100_clr0400.dll
    VB DLL: False   Legal Copyright: © Microsoft Corporation. All rights reserved.
    Loaded Image Name: msvcr100.dll   Legal Trademarks:
    Mapped Image Name:   Original filename: msvcr100_clr0400.dll
    Module name: msvcr100   Private Build:
    Single Threaded: False   Product Name: Microsoft® Visual Studio® 2010
    Module Size: 840 KBytes   Product Version: 10.00.40219.325
    Symbol File Name: msvcr100.dll   Special Build: &
  • Sohaib Cheema Profile Picture
    Sohaib Cheema 49,438 User Group Leader on at

    on LCS you can upload file in zip format, also you may think to restart server, to collect WER logs

  • Mohamad Barada Profile Picture
    Mohamad Barada 180 on at

    Hello dear,

    We are facing the same problem.

    Did you manage to solve this problem? If yes do you remember how did you solve it please ?

    Thanks in advance for your reply.

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Neeraj Kumar – Community Spotlight

We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…

Congratulations to the November Top 10 Community Leaders!

These are the community rock stars!

Leaderboard > 🔒一 Microsoft Dynamics AX (Archived)

#1
Martin Dráb Profile Picture

Martin Dráb 4 Most Valuable Professional

#1
Priya_K Profile Picture

Priya_K 4

#3
MyDynamicsNAV Profile Picture

MyDynamicsNAV 2

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans