Known issues for Analysis

This section contains troubleshooting and known issues for Analysis.


  • If the behavior of Analysis is unpredictable and unexpected messages appear, this might be a result of UAC Virtualization having been enabled for Analysis. You can disable UAC Virtualization on the Analysis.exe process in the Windows Task Manager.
  • Analysis API works only on x86 platforms. If you are using Visual Studio, define the platform as x86 in the project options.
  • When analyzing results from a load test in which the web Vusers accesses the AUT through a proxy server, the Time to First Buffer Breakdown graph shows only zero values for Network Time and Server Time. This is because the "time to first buffer" metric is turned off when working behind a proxy, and the time values can only be calculated to the proxy server.
  • Load results that contain transactions with the '@' or ',' characters may conflict with existing transactions. This is because Analysis attempts to replace those characters with the '_', and if this results in a transaction name conflict, an error will occur.

    Workaround: Avoid using the '@' and ',' characters in transaction names.

  • The following Analysis default settings have been modified: Include Think Time is disabled and Display summary while generating complete data is enabled.
  • When exporting Analysis reports to MS Word, the content load may affect the table format within the document. The recommended format is RTF.
  • If the results take a long time to load, make sure that the Use cached file to store data option in Tools > Options > General tab is disabled. You should only enable this for very large result files. For details, see General tab (Options dialog box).

Back to top


  • When the Analysis results consists of a large number of similar measurements, you may experience spikes in graphs, or an Out of memory message.

    Workaround: For 64-bit Windows, make sure that you have 4 GB or more memory. For 32-bit Windows, select Start > Run, and type msconfig. In the Boot tab, click Advanced Options. Select Maximum memory and set it to the maximum value.

  • After running a Language Pack, the Analysis data generated from the sample session (in the <LoadRunner Professional root>\tutorial folder) is displayed in English and filtering cannot be applied.

    Workaround: Regenerate the graphs.

  • The Transaction Response Time (Percentile) graph may show inaccurate results.


    1. Close the Analysis application.
    2. Open the <LoadRunner root>\bin\dat\percentile.def file
    3. In the [Graph Definition] section, set BasicTableName to an empty string:
      [Graph Definitions]
    4. Open Analysis again and view the graph.

Back to top

ALM integration

  • When trying to save an Analysis session to the ALM repository with CAC on IIS, you may encounter an error message indicating that the session cannot be saved and that the connection is unavailable.

    Workaround: Increase the size of the uploadReadAHeadSize parameter to 16 MB or higher, and restart IIS. You can use the command line: C:\Windows\System32\inetsrv\appcmd.exe set config "Default Web Site" -section:system.webServer/ServerRuntime /uploadReadAheadSize:16777216 /commit:apphost

  • After running a Language Pack, the Analysis data generated from the sample session (in the <LoadRunner Professional root>\tutorial folder) is displayed in English and filtering cannot be applied.

    Workaround: Regenerate the graphs.

Back to top

Microsoft SQL server

  • If you are using your own policy in an MS SQL server, you may need to add your own account to the Analysis database template (in the <LoadRunner Professional root>\bin\dat folder).
  • Analysis may fail to load results created through an MS SQL database, if the decimal separator on the Analysis machine is different from the decimal separator on the MS SQL Server machine (common on non-English operating systems).

    Workaround: Change the decimal separator on Analysis machine to be the same as the MS SQL Server machine.

  • Filtering of transactions for MS Access and SQL queries is limited to 100 transactions.
  • If you are using Microsoft SQL Server 2000, you need to either migrate Analysis data, or upgrade to Microsoft SQL Server 2005. The following tasks describe how to migrate and upgrade.
  • For additional tips relating to SQL Server setup, see SQL Server Express setup.

To migrate legacy Analysis data to a SQL 2005 server:

  1. From the SQL Server Management Studio, using Object Explorer, connect to an instance of SQL Server Database Engine.
  2. Expand Databases, right-click Analysis database, select Tasks\Copy Database.
  3. Follow the instructions in the wizard.

To upgrade SQL 2000 to SQL 2005:

  1. Uninstall SQL 2000.
  2. Install SQL 2005.
  3. Restore Analysis data from backup. See

Back to top

See also: