In part 1 of this series, we covered the basic prerequisites of taking a trace. In this post I'm going to cover some best practices around capturing trace data and how to troubleshoot some common issues that may prevent trace files from being created. The steps below apply to both Dynamics AX 2009 and Dynamics AX 4.0. In part 3 we will be covering the steps necessary to load and review a trace using the Trace Parser tool available on CustomerSource.
There's also a video you might want to check out that goes well with the content covered below.
Video: How to collect a trace within Dynamics AX
Now you're ready to supply these trace files to a support engineer or load them into a tool such as Trace Parser to view the results.
Security is the most common issue that prevents tracing from starting successfully. Below are some things to consider when troubleshooting security issues:
Part 3 of this series can be found here.