Getting the latest default trace from the server
I would like to share this Knowledge Base Article with any person who needs sometimes to gather the latest default trace file from right after simulating an issue.
It’s important to look at the right default trace file when investigating about an issue because sometimes other errors existing in the traces can make the task of identifying the root cause of the relevant problem a hard task.
The investigation can be performed focusing on an error which is not the one which got written to the trace after reproducing the real issue, and the investigation can go back and forth without coming to the expected solution.
Following is the reference to the KBA: