What to do if you have a crash

This post is designed to give a simple set of steps to follow if you ever have a crash situation and you’re not sure how to troubleshoot it. To identify the cause of a crash the most important piece of evidence or log is a memory dump file – you need to set something up before…

0

So your AOS crashed, is hanging, or you just want to see what it’s doing

Ever been in a situation where your AOS crashed? And all you had to show for it was a lousy event log message 1000 which didn’t tell you anything except that it crashed? Or perhaps you’ve just wanted to see what your AOS is actually running at a given moment in time? It could be very useful…

0

Finding the AX user and the X++ call stack from a memory dump the easy way

******** Latest update 11-July-2011 ******** Scripts now allow class and table name resolution ******** This post explains how to find the AX user and the X++ call stack that caused an AOS crash – by using special scripts for WinDbg – before reaching this stage you need to first have captured a memory dump, and then…

6

Finding the X++ call stack that caused a crash

This post explains how to find the X++ call stack that caused an AOS crash – before reaching this stage you need to first have captured a memory dump, and then set up WinDbg ready to do some analysis, we have posts which explain both of those steps: Capturing memory dumps: http://blogs.msdn.com/b/emeadaxsupport/archive/2010/05/12/possibilities-to-create-memory-dumps-from-crashing-processes.aspx Setting up WinDbg:…

2

Finding the AX user that caused an AOS crash

This post explains how to find the ax user that caused an AOS crash – before reaching this stage you need to first have captured a memory dump, and then set up WinDbg ready to do some analysis, we have posts which explain both of those steps: Capturing memory dumps: http://blogs.msdn.com/b/emeadaxsupport/archive/2010/05/12/possibilities-to-create-memory-dumps-from-crashing-processes.aspx Setting up WinDbg:  http://blogs.msdn.com/b/emeadaxsupport/archive/2011/04/10/setting-up-windbg-and-using-symbols.aspx…

0

Setting up WinDbg and Using Symbols

Once you have collected a dump file, to analyse it you need to use a tool called WinDbg. In this post I am going to explain how to set up WinDbg so it’s ready to debug a memory dump taken from a Dynamics AX process. If you’re not sure how to create a dump file,…

2

Possibilities to create Memory Dumps from crashing processes

Sometimes it happens that during regular operation the Dynamics AX Application Object Server (AOS) is suffering from an abnormal program termination, which is better know as a crash. Users connected with the Dynamics AX Client to the affected AOS Instance are noticing such an issue very soon as they get disconnected from the AOS. In…

0

Identifying damaged Table objects in the AOT MetaData

It happens very seldom, but sometimes the AOT MetaData is getting damaged, especially for Table objects. Indications of such an element “corruption” can be that you have one explicit Table in the AOT and every time you access this object either the Dynamics AX Client or the Dynamics AX Application Object Server crashes. But the issue…

1

Identical AX 2009 AUC File Created For Multiple AX Installations

We came across an issue recently where we had the same GUID for two different AX installations running on the same server and therefore only one AUC file existed for both installations instead of two separate ones for use by the AX Client.This caused various anomalies when the client was used to access both instances….

2