SCOM Verbose Tracing

Capture verbose tracing for an Agent or Management Server

This section describes how to capture the trace on the Agent or Management Server.

Prepare for tracing

Logon to the Agent computer or Management Server

Open a command prompt and navigate to the Operations Manager “tools” directory.

Usually located in “%ProgramFiles%\System Center Operations Manager 2007\Tools”

Enter the following command to stop the current trace.

StopTracing.cmd

· In Windows Explorer, navigate to “%windir%\Temp\OpsMgrTrace“, and delete all files in this directory. This is the current and previous trace data, which can be discarded now.

Start tracing

Switch back to the command prompt and enter the following command to start a new verbose trace.

StartTracing.cmd VERNote: “VER” must be capitalized as shown above.

· Keep this command prompt open, as you’ll need to switch back to it in order to stop and format the trace data later.

Wait for issue to reproduce

It is important to wait for the issue to reproduce, and stop tracing immediately after it does. Monitor the problem closely, so that tracing can be stopped immediately after problem occurs.

Stop tracing

Switch back to the Agent or Management Server and enter the following commands in the command prompt we had left open.

StopTracing.cmd

FormatTracing.cmd

· After formatting completes, Windows Explorer should open to the %WINDIR%\Temp\OpsMgrTrace directory, displaying the files containing the trace data.

Select all files and send to compressed folder, as shown below.

· Send the compressed file to your Microsoft support engineer for analysis.
Note: if the compressed file is more than 10MB, as your support engineer to create a FTP workspace to upload the files. Otherwise, it is usually okay to send via email.

Capture verbose tracing for an Operations Manager Console session

This section describes how to capture a verbose trace for a particular Operations Manager Console session.

Prepare for tracing

Logon to the computer in which you’d like to capture a trace of the Console session.

Open a command prompt and navigate to the Operations Manager “tools” directory.

Usually located in “%ProgramFiles%\System Center Operations Manager 2007\Tools”

Note: Administrator may be required to run tracing on client computers, because the trace writes to the Windows directory, which is usually a protected file system. If there are issues with capturing the trace, ensure that the command prompt is launched under the Administrator account, as shown below.

Enter the following command to stop the current trace.

StopTracing.cmd

· In Windows Explorer, navigate to “%windir%\Temp\OpsMgrTrace“, and delete all files in this directory. This is the current and previous trace data, which can be discarded now.

Start tracing

Switch back to the command prompt and enter the following command to start a new verbose trace.

StartTracing.cmd VERNote: “VER” must be capitalized as shown above.

· Keep this command prompt open, as you’ll need to switch back to it in order to stop and format the trace data later.

Wait for issue to reproduce

It is important to wait for the issue to reproduce, and stop tracing immediately after it does. Monitor the problem closely, so that tracing can be stopped immediately after problem occurs.

Stop tracing

Switch back to the computer hosting the console session and enter the following commands in the command prompt we had left open.

StopTracing.cmd

FormatTracing.cmd

· After formatting completes, Windows Explorer should open to the %WINDIR%\Temp\OpsMgrTrace directory, displaying the files containing the trace data.

Select all files and send to compressed folder, as shown below.

· Send the compressed file to your Microsoft support engineer for analysis.
Note: if the compressed file is more than 10MB, ask your support engineer to create a FTP workspace to upload the files. Otherwise, it is usually okay to send via email.