Problem :
If you have a Visual Studio solution where one of the projects is a performance counter DLL, after installing the VTune analyzer and integrating it into Visual Studio, you may find that any attempt to build the DLL fails.

Environment :
Windows*

Root Cause :
The VTune Performance Analyzer, upon start up, launches a helper process, 'vtunecca.exe'.  This helper process collects the list of performance objects and counters available in the system for configuration in preparation for Counter Monitor data collection.  This procedure of loading the performance objects and counters causes all custom performance counter DLLs to be loaded and locked into that process.  Consequently, when an attempt is made to build a custom performance counter DLL, the build fails because the DLL is open for access and cannot be overwritten.

Resolution :
There are a couple of workarounds for this known issue:

1. Un-integrate the VTune analyzer from Visual Studio.  Since the VTune analyzer has a standalone graphic interface, you can un-integrate from Visual Studio and use the standalone GUI to collect data.
   To un-integrate: in the Control Panel, go to Add/Remove Programs and select the VTune Performance Analyzer and then press the Change button. When the dialog opens, select Modify and step through the dialogs pressing Next until you get to the dialog that allows you to uncheck the integrate with Visual Studio option.
2. Rename the vtunecca.exe file prior to starting Visual Studio.  You can find the vtunecca.exe file in the C:\Program Files\Intel\VTune\Analyzer\Bin directory.  Of course, you cannot use the Counter Monitor while the name of this file is changed, but you will be able to build the DLL and test it using other means.
   Simply rename the file back to the original vtunecca.exe and the Counter Monitor feature will begin working again, after restarting the VTune analyzer.

To obtain technical support, please go to Software Support.