After upgrading to the Intel® VTune™ Performance Analyzer 8.0 for Windows, you may receive this error message when attempting to open the source view:

A serious error occurred in file D:VTune5.0analyzersrcSVDPVTSvdp.cpp at line 1526 (Unexpected problem has occurred. The Source View window will now be closed.). The failed HRESULT that produced this error is 0x80340004. Please contact technical support.

This can be the result of left over configuration files. Please exit the VTune analyzer and remove all files of the form vtenv.stg* from the user's VTune application directory, e.g., C:Documents and Settings<userid>Application DataVTune. Now, restart the analyzer and attempt to open the source view, again.

Operating System:

We are aware of problems running the VTune™ Performance Analyzer for Windows* on Apple* hardware using the Parallels* VM and are working with them on a solution.

To avoid this problem, reboot into Microsoft Windows* using Apple's Boot Camp* and run the VTune analyzer under Windows.

We are also aware of processor events that cause the VTune analyzer to crash on Intel® Core™ Duo processors on both Apple and non-Apple hardware. We are working on an update to the VTune analyzer to address this problem and will update this page when it is available. In the meantime, disabling calibration in the sampling configuration may resolve this issue. Please refer to the online help topic Calibration for more information.

Operating System:

Symptom:

If you have integrated the VTune™ Performance Analyzer with Microsoft* Visual Studio* 2005 on a Microsoft Windows Vista*-based system, and you try to configure a sampling activity, you may get a dialog box that says: "a serious error has occurred……".

Cause:

Microsoft Visual Studio 2005 must be run as an administrator on Microsoft Windows Vista-based systems.

Solution:

Run Microsoft Visual Studio 2005 as an administrator. You can do this by right clicking on the desktop icon and choosing the "Run as Administrator" pop up menu item. You may also run the VTune Performance Analyzer outside of the Microsoft Visual Studio 2005 environment without being an administrator.

Recent reports of Visual Studio starting up slowly after integrating the VTune analyzer, even after the VTune analyzer has been uninstalled and un-integrated, have been confirmed. We are investigating a solution and will provide one as soon as we can.

The first course of action is to attempt the following:

1. Install the VTune analyzer for Windows version 9.0 Update 3 with integration into Microsoft Visual Studio*.
2. Using Add/Remove Programs, un-integrate the VTune analyzer from Visual Studio by:
3. selecting Change,
4. then Modify,
5. in the Custom Setup dialog, choose to not make the Visual Studio integration available.

If Visual Studio is still slow to start up, the following steps may provide a workaround. Please only use these steps if you are comfortable with editing the system registry.

1. Determine if the follow files are present:

   VTUNE_INSTALL_DIR/Analyzer/bin/AnalyzerPkg.dll
   VTUNE_INSTALL_DIR/Shared/bin/VpePkg.dll
   VTUNE_INSTALL_DIR/tcheck/Bin/TCVS_Plug.dll
   VTUNE_INSTALL_DIR/tprofile/Bin/TPVS_Plug.dll

   If they are not present, manually copy them from the extracted install package directory (i.e., C:Program FilesIntelDownloadw_vt_p_9.0.016, by default).

2. Set the registry key HKEY_LOCAL_MACHINESOFTWAREIntel CorporationVTune(TM) Performance Environment6.0InstallInfoIntegrateProduct xFlag to 2, where x is 1, 2, and 3.

3. Change directory (cd) to VTUNE_INSTALL_DIR/Analyzer/bin/ and execute Regsvr32 /u AnalyzerPkg.dll

4. cd to VTUNE_INSTALL_DIR/Shared/bin/ and Regsvr32 /u VpePkg.dll

5. cd to VTUNE_INSTALL_DIR/tcheck/Bin/ and Regsvr32 /u TCVS_Plug.dll

6. cd to VTUNE_INSTALL_DIR/tprofile/Bin/ and Regsvr32 /u TPVS_Plug.dll

7. Run ' devenv /setup' and wait for the process devenv.exe to finish. Use Windows Task Manager to monitor the process.

8. Run Visual Studio and verify faster start up.

It those steps don't help, try the following:

1. Create the file vs-clean.reg with the following content (i.e., between the horizontal lines):
   

   ---

   REGEDIT4
   [-HKEY_LOCAL_MACHINESOFTWAREMicrosoftVisualStudio8.0InstalledProductsVTune(TM) Performance Analyzer]
   [-HKEY_LOCAL_MACHINESOFTWAREMicrosoftVisualStudio8.0ToolWindows{64A3F9FB-DE97-4BE9-98E3-D29B8C3FDDED}]
   [-HKEY_LOCAL _MACHINESOFTWAREMicrosoftVisualStudio8.0ToolWindows{790D49F7-DCC4-4D09-A63D-7D3ED59095C5}]
   [-HKEY_LOCAL_MACHINESOFTWAREMicrosoftVisualStudio8.0Packages{0C9EA19B-4D8E-4DC2-8857-BADC8CE59655}]
   [-HKEY_LOCAL_MACHINESOFTWAREMicrosoftVisualStudio8.0Packages{4A1CBBEB-5B65-4D8E-99F9-9C5DA2AE017E}]
   [-HKEY_LOCAL_MACHINESOFTWAREMicrosoftVisualStudio8.0Packages{2D4618D4-7B9E-488E-9AAB-E833B80B47B9}]
   [-HKEY_LOCAL_MACHINESOFTWAREMicrosoftVisualStudio8.0Packages{432B8691-71CE-4D16-82AC-5F683A167B99}]
   

   ---

2. Apply changes by double-clicking on this file in Windows Explorer.
3. Finally, open a Command Prompt, change the current folder to C:Program FilesMicrosoft Visual Studio 8Common7IDE and run " devenv.exe /setup", waiting for the process devenv.exe to complete. Use Windows Task Manager to monitor.

Operating System:

Symptom(s):

The VTune™ Performance Analyzer identifies your DLL as a system DLL. As a result, only exported functions are instrumented.

Cause:

The DLL is located in a address that the VTune analyzer recognizes as a system address. System address ranges are set as follows:

IA-32:
0x58000000 - 0xFFFFFFFF
Intel(R) 64:
0x0000000070000000 - 0x000000007FFFFFFF
0x000007FF50000000 - 0x000007FF7FFFFFFF
IA-64:
0x0000000070000000 - 0x000000007FFFFFFF
0x00000642F0000000 - 0x00000642FFFFFFFF
0x00000643F0000000 - 0x00000643FFFFFFFF
0x000006FAE0000000 - 0x000006FAFFFFFFFF
0x000006FB50000000 - 0x000006FB7FFFFFFF

Solution:

Currently, there are two work-arounds available:

• Change the /BASE: nnn option of the relevant linker session to set value nnn out of the range.
• Run link /edit /rebase:base= nnn userdll.dll to change the base address of the DLL to a value nnn which is out of the system address range.

This issue may be resolved in a future release of the VTune analyzer. At that time, this page will be updated with the release information.