Stopping the IIS Request-Based Tracing Session

  • Article

Applies To: Windows Server 2003, Windows Server 2003 with SP1

Stop the trace session after you have reproduced the problem. If you are unable reproduce the problem, stop the trace session after a few minutes and then review the trace log. Be aware that tracing consumes system resources. On a server processing hundreds of requests per second, the trace log file created by ETW can grow in size to several megabytes after a few seconds, depending on the number of providers defined in the provider file. Immediately disable tracing on production servers after you have gathered enough data to help you isolate and troubleshoot the problem.

To stop the trace session, execute the logman stop trace command from the command prompt. For example:
Logman stop trace ISAPItrace -ets

Note

ETW does not support running multiple trace sessions with the same provider at the same time. You must stop an existing trace session before starting a new one. For example, you can not run two trace sessions where both sessions use the IIS: WWW Server provider.