Microsoft KB Archive/242326

= BUG: Visual Studio Analyzer Does Not Filter by Source Field =

Article ID: 242326

Article Last Modified on 10/2/2003

-

APPLIES TO


 * Microsoft Visual Studio 6.0 Enterprise Edition

-



This article was previously published under Q242326



SYMPTOMS
In Visual Studio Analyzer, when collecting events through a filter that tests the Source field against a string value, no events are collected.



RESOLUTION
Test the Source field against the Source's registered GUID.



STATUS
Microsoft has confirmed that this is a bug in the Microsoft products that are listed at the beginning of this article.



MORE INFORMATION
With Visual Studio Analyzer filters, you can focus the data you use in your application analysis. Through filters, you determine which Visual Studio Analyzer events to collect and which to include in an event log. You define a filter before you start collecting events. After you have collected events, you refine the filter to help you focus on the events that are most important to your analysis.

The following is a valid filter: (Source = "VSA Debug Event Source User") However, no events are collected or displayed. To work around this problem, you must use the source's registered GUID. In the case of VSA Debug Event Source User, the following is correct: (Source = {6C736D00-BCBF-11D0-8A23-00AA00B58E10}) The following is a list of the Microsoft Event Sources and their GUIDs:
 * ADO Event Source - {0000051A-0000-0010-8000-00AA006D2EA4}
 * SQL Server OLEDB - {0C7FF16C-38E3-11D0-97AB-00C04FC2AD98}
 * COMTI Event Source - {67B25210-0867-11D1-8657-0080C790DB95}
 * VSA Debug Event Source User - {6C736D00-BCBF-11D0-8A23-00AA00B58E10}
 * COM Event Source - {95734D90-57A9-11D1-A49C-00C04FB9980F}
 * ODBC Event Source - {AB3C1600-4BF8-11D1-8AB9-00C04FD611CD}
 * JScript Event Source - {AD1C185E-980E-11D1-B739-00C04FC2B085}
 * MTS Event Source - {BACEDF4E-74AB-11D0-B162-00AA00BA3258}
 * VBScript Event Source - {C1BF736F-980E-11D1-B739-00C04FC2B085}
 * Web Event Source - {C9575D00-BC02-11D0-8A21-00AA00B58E10}

NOTE: The above is true for any custom sources that you implement. To filter by a custom source, you must specify the custom source's registered GUID.

