Solution:
This is probably due to a missing event. Only event ratios derived from events that have been sampled and collected as part of an Activity result are available. To fix this problem:
1. Make sure to collect all the related events
2. Drag the events into the source view

Relevant Information:
event ratio

Solution:
Event Ratios are displayed in the summary pane so that the user can select a range of source lines (or assembly language statements) and see the calculated ratios for that range of code. If the user wants to see the value for an individual source line or assembly statement, that line can be highlighted and ratios will appear in the summary pane just below. Note: all the events used to calculate the ratio must have occurred on that line in order to calculate the ratio.

Relevant Information:
event ratio

Solution:
Sampling requires line number and symbol information (debug information) when drilling down from a hotspot view to the source view of a module. Ensure before running an Activity configured with the sampling collector, that debug information is compiled with the binary file. If you do not supply this information, the Intel® VTune™ analyzer disassembles the binary file and displays this information in the source view. It cannot display the source code itself.

Relevant Information:
EBS, Sourceview

Symptom(s):

• ERROR: "Could not connect to remote machine. Connection refused. Error no. (10061)(WSAECONNREFUSED)"
• This is followed by another dialog box titled "Serious Error"

Cause:
Forgot to start VTServer on the Linux side.

Solution:
Start VTServer on the Linux* Side
Other possible causes include:

1. TCP/IP is not running on the Linux server. Confirm that the Linux server is in multi-user mode, since TCP/IP processes don't run in single user mode (sometimes called maintenance mode).
   
   # ps -ef | grep init
   
   The standard output of the above command will show an init statement, followed by a bracketed number. If that number is a [1], that is, anything other than a [2] through a [5], you must bring the system into multi-user mode so that TCP/IP will be active.
   
   
2. TCP/IP names for the two systems are not properly set up.Try pinging between the two computers, both ways. Ping each direction first by IP address, then again by hostname. There should be no lost data packets.
   
   
3. TCP/IP is not properly configured on the Linux system. Confirm the TCP/IP configuration by using the following two commands:
   # netstat -in
   # ifconfig <network card>
   Where <network card> is the non "lo" entry from the netstat command, for example:
   # ifconfig eth0
   Confirm IP address, netmask, and all relevant networking information. Make changes if needed, compared to the TCP/IP setup of the Windows* computer.

Symptom(s):

Any of the following error messages are displayed:

• "Application failed to initialize properly."
• "No results were generated for this run...."
• "Instrumentation is not possible."

Or, after exiting the application being call graphed, the activity does not automatically terminate and, after pressing the Stop button in the analyzer, the analyzer appears to hang.

Solution:

Follow this list of suggested steps to resolve any number of problems that you may encounter when using the call graph feature of the Intel® VTune™ analyzer. They are listed in order of preference:

1. Select the Options item from the Configure menu.
2. In the tree on the left, select Call GraphCollectorCache Directories.
3. Press both of the Clear buttons.
4. Create a new call graph activity and attempt to collect call graph data, again.

1. Select the Options item from the Configure menu.
2. In the tree on the left, select DirectoriesSymbol Repository.
3. Press the View Symbol Repository Files button.
4. Locate your module(s) in the list and click on it.
5. Press the Delete button - this does not delete the file from your system, it only removes the VTune analyzer's knowledge of it so that it will be regenerated.
6. Press OK until all dialog boxes are dismissed.
7. Create a new call graph activity and attempt to collect call graph data, again.
   Note: If the problem persists, view the Symbol Repository files again and ensure that the correct symbol file is associated with the module(s) in question.

1. Open your module(s) with the Static Module Viewer, by selecting Open Static Module Viewer from the File menu.
2. Review the module and function list to ensure that the expected routines are present with the Functions with source check box checked.
3. If modules or functions are missing, ensure you have created a binary with debug information and that it is correctly identified by the VTune analyzer in the Symbo l Repository (see section B above).

1. Select the Options item from the Configure menu.
2. In the tree on the left, select Call GraphCollector.
3. Set the Default Instrumentation Level of User EXEs and User DLLs to Minimal.
4. Create a new project using the Call Graph wizard, specifying your application, and attempt to run the activity.
5. If the execution of your application is successful (regardless of whether any results were generated), begin to increase the instrumentation level of specific modules of interest by modifying the activity and configuring the call graph collector.

Operating System:

Selecting Don't calibrate Sample After Value (SAV) in the Configure Sampling dialog and specifying a very low SAV, so that a high number of samples per second is collected (we usually recommend 1000 samples per second), may cause the following error message to appear after sampling completes:

Error: An error occurred during drill-down. Cause of error cannot be determined.

Also, the message " The Sampling Collector failed to collect data because SAV is too low " is displayed in the Output window just before sampling data collection begins.

Generating a high frequency of samples causes many interrupts per second to be generated. This in turn can slow the system down beyond use and can even cause the system to hang.

Solution:
Use Calibrate Sample After Value for all the selected events option to generate appropriate SAVs before running sampling data collection.

Note: This will require an additional run of the activity for each set of events to collect. The number of anticipated runs is displayed in the Configure Sampling dialog on the Events tab.