Tracer parser error "This trace doesn't contain a session which can be analyzed."

(0) Share

Report

Posted on by Community Member

I am trying to use trace parser and my user account is associated with "System Tracing user". After I downloaded the trace to a local directory and open the "Dynamices 365 Unified Operation Trace Parser" tool to open the trace, I got the error "This trace doesn't contain a session which can be analyzed.".

How do I resolve this? If this is not the tool to read the trace, what it would be? I tried to user "Captured trace" within F&O but it didn't show trace I captured.

I have the same question (0)

All responses (8)

Answers (1)

Fangyuan Hou on at

Like (0)

Report

Hi Yvonne,

The tool is right, this maybe because the trace you captured is too short without a session, what's the size of the trace file? What operation you did when you take the trace.

The captured traces button can only be seen by users with administrative rights and you can only see the trace in "captured trace" after someone Upload trace.

https://docs.microsoft.com/en-us/dynamics365/fin-ops-core/dev-itpro/perf-test/trace-trace-tutorial

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

The size of trace is 275456 KB, I was trying to capture the actions of creating interest note.

Was this reply helpful? Yes No
Fangyuan Hou on at

Like (0)

Report

Can you try to open the AX trace on the VM which has same version of the environment to see whether it works?

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

Hi Fangyuan, could you be more specific on how to find that? Thx!

Was this reply helpful? Yes No
Fangyuan Hou on at

Like (0)

Report

Hi Yvonne,

You can get the version info after click the question mark. Please feel free raise a ticket to us if you need a further troubleshoot on this.

Was this reply helpful? Yes No
Verified answer

rolandsteber 55 on at

Like (0)

Report

Hi Yvonne,

Today I ran into the same error!
The strange, but effective solution: Delete and recreate the TraceParser database and voilà - the traces are saved correctly again!

Kind regards,

Roland

Was this reply helpful? Yes No
Suggested answer

Shahil 635 on at

Like (0)

Report

I recently came across this issue as well.

I refreshed the page (F5) and ran the trace again - it worked.

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

Thank you, it works!!

Was this reply helpful? Yes No