When you are setting up tracing from the Configuration Utility or Server Configuration Utility, be aware of the following:

Note
Tracing is processing-intensive and space-intensive - We recommend that you do not turn tracing on for more than one client at a time.

• On Windows Vista and Windows Server 2008 operating systems, only Administrators and SYSTEM accounts can use tracing. To run tracing on a client, you must choose the option run as Administrator. To run tracing on the server, the AOS account must be a SYSTEM account.

• The log directory cannot be changed - The log is always installed to installationdirectory\log. Restrict access to the directory to administrators and the AOS account (the domain account or Network Service account associated with the AOS service).

• Trace files are stored in binary format, and can be read with the Microsoft Dynamics AX Tracing Utility.

1. Open the Server Configuration utility ( Start> Administrative Tools> Microsoft Dynamics AX Server Configuration Utility).

2. Verify that the currently selected Application Object Server (AOS) instance and configuration are the ones you want to modify.

3. On the Tracingtab, evaluate the type of tracing you need to do, and choose settings.

   To do this	Select these options
   Monitor general performance on a production server	RPC round trips to server
   Perform standard troubleshooting	RPC round trips to server X++ method calls, Number of nested calls: 4 SQL statements Allow client tracing on Application Object Server instance
   Debug code	RPC round trips to server X++ methods SQL statements Row fetch summary (count and time) Allow client tracing on Application Object Server instance
   Deep troubleshooting	All options. Performance may be degraded while all tracing options are on.

4. On the Tracingtab, click Start trace. If the AOS Windows service is running, the trace starts within 15 seconds. If the service is stopped, the trace starts the next time the service is started.

1. Open the Configuration utility ( Start> Control Panel> Administrative Tools> Microsoft Dynamics AX Configuration Utility).

2. Verify that the currently selected configuration is the one you want to modify.

3. On the Tracingtab, evaluate the type of tracing you need to do, and choose settings.

   To do this	Select these options
   Monitor general performance on a production server	RPC round trips to server
   Perform standard troubleshooting	RPC round trips to server X++ method calls, Number of nested calls: 4 SQL statements
   Debug code	RPC round trips to server X++ methods SQL statements Row fetch summary (count and time) Enable method tracing to client desktop
   Deep troubleshooting	All options. Performance may be degraded while all tracing options are on.

4. To start tracing once you have set the options you want, close the Configuration Utility, and restart your Microsoft Dynamics AX client.

Files from traces are saved to the following locations:

A new file is created each time tracing is started, or when a new day starts.

Note
If you are running frequent traces, be sure to remove or archive unneeded trace files often.

This section provides information on troubleshooting issues encountered while tracing.

In the Configuration Utility it appears that a trace is running, but when I look in Windows, the trace is not running

When I run more than one client tracing session at a time, my system slows down