Resolving TraceView Errors

This topic describes errors that TraceView commonly reports and suggests solutions. It is not intended to be a complete troubleshooting guide.

Trace provider is not added

If TraceView cannot find a PDB symbol file or a trace message format (.tmf) file for the trace provider, it does not add the trace provider to the provider list in the Create New Log Session dialog box, and it does not display a message that explains why the provider was not added.

If the provider does not appear in the provider list after you try to add it, restart the procedure and, in the Format Information Source Select dialog box, click Select TMF Files instead of Set TMF Search Path. If you cannot locate a PDB file or a TMF file for the provider, you cannot use TraceView to create a trace session with the provider.

Failed To Enable Trace For Control GUID: guid

This error typically occurs when more than one trace consumer is collecting events from a single trace provider on the system. To resolve this conflict, display all trace sessions that are running on the computer, and stop sessions that are conflicting.

To display all trace sessions on the computer, in a Command Prompt window, type traceview -l. (The TraceView window displays only the trace sessions that are running in TraceView.) The resulting display lists the active sessions.

To stop a trace session, in a Command Prompt window, type traceview -stopSessionName.

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

Cannot open logfile for reading

This error occurs when you try to display an existing trace log for a trace provider that is providing events for a real-time trace session or another existing trace log in TraceView.

TraceView can create only one trace session or display one trace log for each trace provider.

Cannot connect to any trace session in the group

This error typically appears when you try to group trace sessions that cannot be grouped. For example, it appears when you try to include a real-time trace session in a group on a version of Windows earlier than Windows Server 2003.

To resolve this error, review the Limitations of Grouping topic and include only trace sessions that you can group on your system.

Internal error: CloseTrace error 170

This error occurs when you try to join an NT Kernel Logger trace session that is already in progress. You can use TraceView to create an NT Kernel Logger trace session, but you cannot join an NT Kernel Logger trace session that is started by a tool or method other than TraceView.

For more information, see Joining a Trace Session and Creating an NT Kernel Logger trace session.