In part 1 of the series I discussed the basic prerequisites for capturing an AX trace. In part 2, I discussed how to collect a trace. In this post I’ll walk you through the process of importing a trace into Trace Parser and show you a few different things I look for when I start analyzing a trace for performance issues.
First, you’ll need to download and install the Trace Parser tool from CustomerSource.
Here are a couple of quick notes on installing the tool:
At this point I’m assuming you've already collected a trace and installed Trace Parser. Now we’re ready to import a trace and review it.
Client Trace (copy the ServerNext line)
Server Trace (paste anywhere in the call tree tab to get the associated line)
As you can see, this tool provides lots of useful information about how your code is performing. Hopefully I covered enough of the basics to get you started!
For some Trace Parser troubleshooting tips, see part 4.
While importing taces in Trace Parser I am getting error that 'Trace doesn't contain any session'. Can you help me solving this issue.
i have the same issue "Trace doesn't contain any session"
Where i wrong ?
Hi Great article
You just have to add the credentials at the database server for the user that starts the trace parser and therefore must create the DB
I have the same issue both for the client trace and the AOS trace - "Trace doesn't contain any session"
I import server trace (AX 2009) but I still can't see the sql tab. Could you advise what's wrong?
I also get "Trace doesn't contain any session". I'm using 2012 version of the tracer with an AX 4 trace file.
Does anyone have an idea what might be wrong?
Why is it I don't get any code in the "Context" area?
Thats because you don't have dbowner permission on that DB
How do you get beyond the "Trace doesn't contain any session" error?
Solved the nagging "Trace doesn't contain any session" by creating the trace database on a local instance of SQL server.
Its is very useful and great explanation. Thanks Dayakar Reddy, Bangalore