Article ID: 926098 - Last Review: September 28, 2011 - Revision: 7.0 How to enable COM+ and COM diagnostic tracing
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. On This PageINTRODUCTIONEvent 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:
MORE INFORMATIONStart tracing for the COMSVCS, COMADMIN, and DCOMSCM providersTo start the tracing for COMSVCS, COMADMIN, and DCOMSCM providers, run one of the following commands as appropriate at the command prompt:logman -start comsvcs -p {B46FA1AD-B22D-4362-B072-9F5BA07B046D} 0xf 0x5 -ets logman -start comadmin -p {A0C4702B-51F7-4ea9-9C74-E39952C694B8} 0xf 0x5 -ets logman -start dcomscm -p {9474a749-a98d-4f52-9f45-5b20247e4f01} 0x7 0x5 -ets Start tracing for the OLE32 providerImportant 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
(http://support.microsoft.com/kb/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.
After you enable OLE32 tracing, start the tracing by running the following command at the command prompt: logman -start ole32 -p {bda92ae8-9f11-4d49-ba1d-a4c2abca692e} 0xf 0x5 -ets Stop tracing for all providersImportant 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 locationThe 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.Next Steps
REFERENCESFor more information about COM and COM+ tracing, visit the following MSDN Web site: http://blogs.msdn.com/distributedservices/archive/2009/06/19/tracing-in-com-and-complus.aspx
(http://blogs.msdn.com/distributedservices/archive/2009/06/19/tracing-in-com-and-complus.aspx)
APPLIES TO
| Other Resources Other Support Sites
CommunityGet Help NowArticle Translations
|






Windows Live
Facebook
Twitter
Linkedin
Digg it
Yahoo
Delicious
StumbleUpon
Yammer
Reddit
Technorati
FriendFeed
Email
Back to the top
