How to Trace All Requests Currently Executing in IIS Worker Processes

  • Article

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

Use currently-executing requests tracing to find out which requests are executing in a worker process when the worker process has become slow or unresponsive. When enabled, currently-executing requests tracing prompts worker processes to report statistics and details about each request in each worker process.

Currently-executing requests tracing does not require a provider file. Instead, currently-executing requests 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.

-p “IIS: Request Monitor”

Identifies which provider (-p) should be traced.

-ets

Tells Logman.exe to start the trace session immediately.

To trace all requests currently executing in IIS worker processes

  1. Open a command window and type logman start session name –p “IIS: Request Monitor” -ets and press ENTER.

  2. 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), and whether or not the command was successful.

  3. 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.

  4. From the command prompt, type logman stop session name -ets and press ENTER.

    To view the trace data, see How to Process and View Trace Log Files.