There are two things to keep in mind while tracing.
1. Tracing uses additional resources on the Root Management Server.
2. Stop tracing as soon as the issue has been reproduced.
This method has only been testing in SCOM 2007 SP1 and R2.
1. Logon to the Root Management Server
2. Open a Command Prompt and navigate to %ProgramFiles%\System Center Operations Manager\Tools. (keep this command prompt open to this locations until you have stopped tracing)
3. Issue the following command
4. Open explorer and navigate to C:\WINDOWS\temp\OpsMgrTrace.
5. You should see 10-20 *etl, *log and *sum files.
6. While still in explorer, navigate to %ProgramFiles%\System Center Operations Manager\Tools.
7. Make a copy of TracingGuidsBID.txt.
8. Then open TracingGuidsBID.txt. Comment all lines by typing # before each line, except for:
9. Save and close TracingGuidsBID.txt.
10. Go back to the Command Prompt and issue the following commands:
TraceLogSM.exe -stop TracingGuidsNative
TraceLogSM.exe -stop TracingGuidsUI
11. You are now tracing the Notification Channel components. Continue tracing until the issue has been reproduced.
12. When the issue has reproduced, immediately issue the following command to stop tracing. If tracing isn’t stopped immediately after reproduction, you may risk rolling the log file.
13. While still in the command prompt, issue the following to format the output
14. After formatting has completed, explorer should open at the location where the formatted files were copied to.
Gather Data and Send to Microsoft
Now we’ll package this data and send it to Microsoft. If you have a good understanding of ETL logs and OpsMgr error conditions, you may be able to decipher the log yourself.
1. Gather the *etl, *log and *sum files that were formatted and copied to the trace output directory from step 14 above.
2. Gather the Operations Manager event log from the Root Management Server.
3. Zip these files and send to Microsoft.
4. Make note of the Alert Id for which the alert notification was expected, and send that along with the zipped files or in separate email.
5. Include any other data you feel is relevant. Screenshots of Alert History or duplicate tickets in ticketing system, any logging you’re performing beyond Operations Manager, etc.
Note: Upload the files to the secure FTP site that was provided by Microsoft.