Warning You should not enable tracing functionality on production systems unless a Microsoft support representative indicates that the tracing information is required to diagnose an issue. The performance of the computer may be affected. As soon as the reason for the issue is found and resolved, you should disable tracing functionality. By default, tracing functionality is disabled. Therefore, there is no performance effect on a regular installation.
Event Tracing for Windows (ETW) provides a mechanism to trace and log events that are raised by user-mode applications and kernel-mode drivers. In Windows Server 2003 Service Pack 2 (SP2), in Windows Vista, or in newer Windows operating systems, you can use ETW to trace events for some COM+ components and for some base COM components. COM tracing can help you troubleshoot issues that are related to permission, activation, or registration.
The tracing mechanism produces a binary file. The binary file must be formatted by Microsoft so that it can be analyzed.
You can trace the following COM+ and COM providers:
This article describes how to enable and collect diagnostic trace output for COM+ and COM components in Windows Server 2003 SP2, Windows Vista, and newer Windows operating systems.
Start tracing for the COMSVCS, COMADMIN, and DCOMSCM providers
To start the tracing for COMSVCS, COMADMIN, and DCOMSCM providers, run one of the following commands as appropriate at the command prompt:
Important This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft Knowledge Base:
322756 How to back up and restore the registry in Windows
By default, OLE32 tracing is not enabled. Therefore, you must enable OLE32 tracing before you can start tracing. You can do this by adding the required registry entries as described in this section. You can enable OLE32 tracing on all processes that use OLE32 or on specific processes. OLE32.dll is loaded in many processes, and enabling tracing for all processes may cause decreased performance. Therefore, we do not recommend enabling tracing for all processes.
At the command prompt, run the following command to enable OLE32 tracing on all the processes that use OLE32:
Note You can type multiple executables in the registry value. You must type the full path of each executable. Notice the use of double quotation marks and the null terminator (\0). After enabling OLE32 tracing, you must restart the process for the change to take effect.
After you enable OLE32 tracing, start the tracing by running the following command at the command prompt:
Important You must stop the tracing so that the buffer is written to disk. To do this, run one of the following commands as appropriate at the command prompt:
logman -stop comsvcs -ets
logman -stop comadmin -ets
logman -stop dcomscm -ets
logman -stop ole32 -ets
Log file location
The start command will create a log file that has an .etl extension, such as Dcomscm.etl, Ole32.etl, and so on, in the current directory. You can use the -o option to change the output path when you run the start command.
The binary file must be formatted by Microsoft so that it can be analyzed. Please forward the .etl files to your support contact. For more information about how to contact Microsoft Customer Service and Support, click the following article number to view the article in the Microsoft Knowledge Base:
295539 How and when to contact Microsoft Customer Service and Support
Delete the registry key after the trace session is completed.
At the command prompt, run the following command to disable OLE32 tracing on all the processes that use OLE32: