Skip to main content

Tracing

In most support scenarios, it is best to provide a trace of any technical issue to facilitate the investigation,

A trace contains a capture of the execution of a time range that can be used to investigate your issue.

Tracing is a standard D365 F&O feature, for more information please refer to official MS document Trace Tutorial

note

The user taking the trace will need to be granted tracing permission in the matching environment. The administrator can also grant rights to other users to take a trace.

Keep in mind​

Trace file content​

A trace captures all SQL and code statements running while the trace is being recorded, on a single AOS server. This implies trace files will include process of the current session but also any other session running on the same AOS server. If processing triggers an operation on another AOS server (Asynchronous calls / Batches / SysOperation) will not be captured.

Only completed code statements and queries will be recorded: If the recording is stopped during a long-running query, it will not appear in the trace file as it was still running when trace ended.

File size limitats​

D365 trace files are limited to 1.0 Gb. Once the trace file reaches it's limit, the first events are dropped from the file to keep a recording of 1.0Gb size until recording stops.

To keep trace file size to a minimum, we recommend running processes in isolation with as little users/batches running at the same time.

How to​

All steps to re-produce the issue should be performed a first time before running the trace. After reproducing the issue, start the trace, perform the action a second time and stop the trace.

Screenshot

Screenshot

Screenshot

Getting a trace​

Once the trace has been stopped, the following actions are available:

Screenshot

  • Download trace: Store the captured trace on a local machine. You can analyse a downloaded trace by using the desktop version of Trace parser.
  • Support: Open Eftsure support feature, attaching current trace to the support request.
  • Upload trace: Store the trace in the cloud for later download by, for example, the admin. Uploaded traces are automatically deleted after seven days. They can also be manually deleted from the Captured traces page.
  • Return to main menu: Return to the main tracing menu to start another trace.

Trace user information​

A D365 trace captures sessions from every user active on the server during the entire trace. To investigate traces related to a single session, we can filter tracing information on specific users or actions.

Please provide session information alongside traces:

Hit the Feedback button:

Screenshot

The feedback form will popup with the session and Telemetry information to be added to the support ticket

Screenshot

Alternatively find the corresponding TelemetryID, navigate to System administration > Users > Users, find the matching user and provide the Telemetry ID field. This approach helps identify the user in the trace file.

Screenshot

Support​

Traces are also available to attach to support tickets. When requesting support, a trace section is available to include into the ticket attachments.

Screenshot

Attach any trace to your support ticket to help with our investigation.

See Key user support

Email attachments​

If the email file is too large for emails, please share the file via oneDrive or any other large sharing file tool.

Advanced​

Tracing affinity​

If traces are being triggered from the wrong AOS, the trace file will likely not contain the data required for investigation.

To trace on a specific AOS, you'll need to change the AOS connection affinity in your browser:

  • Hit F12 to open the Developer Tools.
  • Go to the Application tab, expand Cookies.
  • Find the cookie matching with your environment name
  • Find the ms-dyn-affinity cookie and change AOS value to match desired AOS.
  • Refresh your page
  • Hit the Feedback button
  • Confirm connection to expected AOS
  • Trigger trace on the appropriate AOS

Screenshot