Dynamics AX has a tracing feature that allows you to generate ETW traces of the client and server activity on your system. The information collected in these traces includes a call tree, SQL statements, and durations for all of the different code that executes. This kind of trace data can be extremely useful when troubleshooting performance issues, but there are a few things you need to know in order to be successful in capturing useful trace data and analyzing it. This is the beginning of a series of posts that cover tracing topics. In this post I'll talk about some of the prerequisite settings necessary to implement on your system. In future posts I'll discuss topics such as tracing best practices, troubleshooting trace collection issues, installing and troubleshooting the Trace Parser tool, and trace analysis basics. There's also a video you might want to check out that goes well with the content below.
Video: How to collect a trace within Dynamics AX
Now to the details...
Generally when I'm tracing something in AX, I try to localize all of my activity on a single isolated AOS. To isolate my activity I prevent other users from connecting to the AOS instance and I run the client directly from the AOS server. I've found that this is the most convenient and reliable way to setup tracing. The prerequisite settings for a successful trace are covered below.
Tracing Prerequisites for the AOS Instance
From the Dynamics AX Server Configuration Utility > Tracing tab, set the following options:
You'll also need to verify that the following AOS registry settings exist and have the recommended values. If something doesn't exist, you will have to create it.
AOS Server Registry Path:
REG_SZ (String Value)
1024 if server has 2GB RAM or more. 512 if server has less than 2GB RAM.
Between 1024 (1GB) and 10240 (10GB) depending on space available.
Tracing Prerequisites for the AX Client
From the Dynamics AX Configuration Utility > Tracing tab, set the following options:
You'll also need to verify that the following AX client registry settings exist and have the recommended values. If something doesn't exist, you will have to create it.
AX Client Registry Path:
Security Considerations for Tracing:
Part 2 of this series can be found here.
In part 1 of the series I discussed the basic prerequisites for capturing an AX trace. In part 2 , I
Superb post Tom Stumpf, i was looking for this from very long...
Los dos problemas más frecuentes que nos reportan con Trace Parser son
How do I change the filesize in an AX 2012 environment - I can't see any registry paths that matches.
@Erik: How are you collecting a trace in AX2012? If you are using the client cockpit, then it is specified there. If you are using perfmon, then it is one of the options by right clicking on the name of the data collector set.