TraceView Limitations

This topic describes the limitations of TraceView.

TraceView Window Limitations

The TraceView window can display and control only trace sessions that are started by using the window. To list and control all trace sessions on the system, use the TraceView command-line interface.

When you exit TraceView, it stops all running (or real-time) trace sessions that you started by using TraceView. To start trace sessions that run independently of the TraceView window, use the TraceView command-line interface.

You can use the TraceView command-line interface and other software tracing tools, such as Tracelog, to control a trace session that TraceView started. However, if you use these other tools to change the properties of a running trace session, TraceView stops the trace session, even if you change properties that can be changed while a trace session is running. When you use TraceView to restart (or join) the trace session, it updates the properties.

TraceView Command-Line Limitations

When you submit a TraceView command in a Command Prompt window, TraceView opens a new Command Prompt window to display its output. You cannot suppress these additional windows.

ETW Limitations

TraceView and other tracing tools based on Event Tracing for Windows (ETW) can create only one trace session or display one trace log for each trace provider. If you try to create a trace session or display a trace log with a provider that is already enabled in TraceView, TraceView displays an error message. For more information about this error message, see Resolving TraceView Errors.

Global Logger Trace Sessions

The TraceView window does not have an option for starting a Global Logger trace session. However, you can use the window to start a Global Logger trace session by entering the Global Logger control GUID, e8908abc-aa84-11d2-9a93-00805f85d7c6, or by saving the control GUID in a control GUID file. For more information about these procedures, see Creating a trace session with a Control GUID and Creating a trace session with a CTL file.

You can also use the TraceView command-line interface to start a Global Logger trace session. Use the following command to start a Global Logger trace session. The word "GlobalLogger" in this command is case-sensitive.

traceview -start GlobalLogger [parameters]

For more information about TraceView commands, see TraceView Control Commands.

Enabling Trace Providers

TraceView automatically enables the trace providers that you add to the trace session. However, after you create a trace session, you cannot use the TraceView window to enable additional trace providers for the trace session or to selectively disable the trace providers that you added to the trace session.

To enable or disable providers, use a traceview -enable command. For more information about this command, see TraceView Control Commands.

Windows XP Limitation

On Windows XP, you cannot include a real-time trace session in a trace session group. This limitation is not affected by service packs.

Windows 2000 Limitations

The following limitations apply only to Windows 2000:

  • Only one trace session can be active at a time.

  • The provider must be running before TraceView starts the trace session.

  • You cannot change the properties of a trace session (or of its trace providers) while the session is running.

Send comments about this topic to Microsoft