How to Trace Requests in IIS
Applies To: Windows Server 2003, Windows Server 2003 R2, Windows Server 2003 with SP1
If you are actively troubleshooting a problem in IIS and you believe the problem exists in a specific component like ASP or the SSL Filter service, you can trace requests in that component to locate the source of the problem. If you are uncertain where the problem exists, you can trace requests in multiple components and view the resulting trace data to locate the source of the problem.
Request-based tracing uses the following commands or switches:
logman start |
Starts the trace session using Logman.exe as the controller. |
logman stop |
Stops the trace session. |
session name |
Any name you want to give this trace session. |
-pf provider file name |
Identifies the name of the provider file. This can also be a path to the file. For more information, see How to Create a Provider File for Request-Based Tracing. |
-ets |
Tells Logman.exe to start the trace session immediately. |
To trace requests in IIS components
From a command prompt, type logman start session name -pf provider file name -ets and press ENTER.
For example: logman start ASPtrace -pf ASPproviders -ets
Event Tracing for Windows prints to the screen details about the trace session you just started, including the name of the session, the file name where the trace data will be collected (session name.etl by default), the providers listed in the provider file, and whether or not the command was successful.
Allow the trace session to run until you have reproduced the problem or until your sites have processed enough requests to produce a manageable data set.
From the command prompt, type logman stop session name -ets and press ENTER.
See Also
Tasks
How to Process and View Trace Log Files