BUG: Visual Studio Analyzer Does Not Collect COM+ Events (257369)



The information in this article applies to:

  • Microsoft Visual Studio, Enterprise Edition 6.0, when used with:
    • the operating system: Microsoft Windows 2000

This article was previously published under Q257369

SYMPTOMS

When you use Visual Studio Analyzer to analyze your application, you are unable to collect COM+ events.

CAUSE

The COM+ Event Bridge does not have the necessary permissions to subscribe to COM+ events.

RESOLUTION

To resolve this problem, add the Visual Studio Analyzer user to the Administrator group. You can determine the Visual Studio Analyzer user by using Dcomcnfg.exe as follows:
  1. Start Dcomcnfg.exe.
  2. Select MSVSA Local Event Concentrator Class from the list of applications.
  3. Click the Properties button.
  4. Select the Identity tab. Note the user, and then close Dcomcnfg.exe
Add the Visual Studio Analyzer user noted in the previous procedure in step 4 to the Administrators group as follows:
  1. Open Control Panel.
  2. Open Administrative Tools.
  3. Open Computer Management.
  4. In the tree view, expand System Tools, and then expand Local Users and Groups.
  5. Select the Groups folder.
  6. Select the Administrators group. From the Action menu, select Add to Group.
  7. Click Add..., and then select the Visual Studio Analyzer user noted earlier.
  8. Click Add, and then click ok.

STATUS

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

MORE INFORMATION

The COM+ 1.0 Event Bridge is included in the Windows 2000 Platform SDK. It consists of one file called Vamts.dll that must be manually registered. See the COM+ 1.0 Event Bridge Readme.rtf file in the Platform SDK for additional information.

REFERENCES

For additional information, click the article number below to view the article in the Microsoft Knowledge Base:

257382 Visual Studio Analyzer Does Not Collect Performance Monitor Events


Modification Type:MajorLast Reviewed:10/20/2003
Keywords:kbBug kbEEdition kbpending kbVSVisAnalyzer KB257369