Micro Focus LoadRunner

Software Version: 12.56


Publication date: February 26, 2018


The following sections provide information and known issues for LoadRunner 12.56.

What's New in LoadRunner 12.56

LoadRunner 12.56 includes many new features, enhancements, and usability improvements.

You can find information on What's New for this version in the LoadRunner Help Center.

For information about the features in previous versions, use the following links.

Installation and configuration information

You can find information and components for installation as follows:

Installation permission requirements:

Notes and limitations

This section includes pre-installation notes, issues, and workarounds for LoadRunner version 12.56.

For additional limitations and workarounds, see the Troubleshooting and Limitations sections in the Help Centers.

Installation and upgrade

Virtual environments

The architectures provided by virtualization vendors are rapidly evolving. LoadRunner is expected to function as designed in these changing environments, as long as the third-party vendor guarantees full compatibility of the virtualized environment with the LoadRunner-approved hardware requirements.

If you follow the LoadRunner system requirements and support matrix to create the virtual machine, LoadRunner will work correctly.

Working on top of a virtual machine may require access to the virtualization server hardware/monitoring environment to ensure the virtualization server is not saturated; otherwise, this might obscure the virtual machine's measurements and lead to false results.


  • LoadRunner version 12.55 must be installed before you can install LoadRunner version 12.56.

  • Default Certificate update: The default LoadRunner certificates have been updated in 12.56. If you are not upgrading all your LoadRunner components to version 12.56, and you use the default LoadRunner certificates, you may have connection issues.

    Resolution: On an upgraded machine, copy all certificates in <LoadRunner root>\dat\cert. Paste them to the same location on all non-upgraded machines.

  • During the LoadRunner 12.56 upgrade, updated versions of the xstream and log4j JAR files are installed.

    Recommended: Manually remove the following older versions of these files, located in the <LoadRunner root>\lib folder:

    • xstream-1.4.8.jar
    • log4j-api-2.4.1.jar
    • log4j-core-2.4.1.jar


  • If you have an older version of VTS, uninstall it and reinstall the latest version from the Additional Components folder in the installation package.
  • If you have multiple LoadRunner components installed together on a machine (for example, both VuGen and Analysis, standalone versions), and you uninstall one of the components, run a Repair installation on the remaining components after the uninstall.
  • If you have VuGen standalone and BPM installed together on a single machine, and you uninstall BPM, run a Repair installation on VuGen.


  • A Red Hat Enterprise Linux (RHEL) 7 (or later) OS is required for running JavaScript Web HTTP/HTML scripts.
  • When uninstalling a load generator on a Linux machine, the uninstall process may fail and the following message may appear: "Error: failed & because &: cannot restore segment port after reloc: permission denied."
    Resolution: Use the setenforce 0 command to disable SE Linux before uninstalling the load generator. When the uninstall is complete, use the setenforce 1 command to enable SE Linux.

Coexistence with Unified Functional Testing (UFT) and UFT Pro (LeanFT)

  • It is not recommended to install LoadRunner and UFT Pro (LeanFT) on the same machine. Doing so may cause issues when invoking the Analysis API from an external code or plugin (for example, Jenkins), with recording and code generation for Java protocols, with Network Virtualization replay, TruClient functionality, and other issues. If you try to continue to work while these issues exist, it may cause LoadRunner to malfunction.

    Possible workaround: Before proceeding, make sure that LeanFT is excluded from the PATH environment variable on the machine. For more information, see this Knowledge Base article.

  • If you install or uninstall LoadRunner on a machine where UFT is installed, at the end of the process a warning message is displayed: "Cannot load resource file <somepath>/mdrv_res.e2 (<somepath>/mdrv_res.j2)." Ignore this message.

  • If you install LoadRunner and UFT on the same machine, and then uninstall one of them, the remaining software program may not function correctly.

    Resolution: Run a Repair of the software program you want to use on the machine.

  • A machine with LoadRunner and UFT, on which UFT was installed after LoadRunner, may not allow the recording of certain protocols, such as Ajax Click & Script.

    Resolution: Uninstall UFT and run a Repair on the LoadRunner installation.

  • If you install UFT on a load generator machine when the load generator agent is running, the remote Controller may not be able to run UFT scripts on the load generator machine.

    Resolution: After installing UFT, restart the load generator agent using the Agent Configuration utility, or alternatively reboot the machine.

Windows 10 (Creators Update) and Windows Server 2016 Operating Systems

  • When working with Windows 10 or 2016, we recommend using Internet Explorer (IE) 11 as the default browser; using the Edge browser interferes with some of the advanced functionality.

  • Use IE as the default browser with Windows 10 to prevent issues with proxy recording and certificate settings.


  • Where applicable, we recommend using TruClient Firefox or Chromium on Windows 10 and Windows 2016.
  • (Windows 10 + IE) TruClient script conversion to Web - HTTP/HTML is not supported on Windows 10 using the IE browser.
  • (IE) The TruClient IE cache simulation mechanism is not supported on load generators running on Windows OS systems installed with KB3000850, Windows 10, or Windows Server 2016. As a result, when running TruClient scripts in IE on a load generator with one of these operating systems, the browser’s cache may not function as expected. This may cause inconsistent server load and measurements.

    Resolution: Remove Microsoft KB3000850 (not relevant for Windows 10 or Windows 2016).


(Windows 10 + IE) WinINet recording mode is not supported on Windows 10. An empty script will be generated.


  • When recording mstsc.exe on Windows 10, if the RDP server side enables FIPS, the default recording will produce the following error: "Because of an error in data encryption, this session will end. Please try connecting to the remote computer again."

    Resolution: Turn off FIPS on the server side, or perform the following procedure to enable recording using the SSL mode:

    1. Open mstsc, enter the IP address of the RDP server, click Show Options to expand the dialog box, and then click Save As to save the configuration to a file. Name the file RDPConfig.RDP.
    2. Open RDPConfig.RDP with Notepad, add enablecredsspsupport:i:0 at the bottom. Search for authentication level in the same file, make sure this line is authentication level:i:2.
    3. Go to <LoadRunner root>\dat\, open rdp_ro.ini with Wordpad or Notepad++ (do not use Notepad because of the new line characters issue), add SupportSSL=1 at the bottom.
    4. In VuGen, click Start Recording. In the Remote Desktop Connection dialog box, click Show Options. Click Open, and choose the RDPConfig.RDP file that you saved above. Then click Connect.

Protocols not supported

The following protocols are currently not supported on Windows 10 or Windows 2016:

  • RTE (Remote Terminal Emulator)


  • Ajax - Click and Script: Replay is supported, Recording is not supported


VuGen and protocols


Controller and General


Network Virtualization and NV Insights Report

Help and PDFs

Non-English operating systems



Deprecated features and protocols

This section provides information about features and protocols whose support was partially or fully discontinued, or will be discontinued in future versions of LoadRunner and Performance Center.

Removed features

The following features were removed from LoadRunner in version 12.53:

Note: In 12.53, the Mobile Application - HTTP/HTML protocol was unified with the Web - HTTP/HTML protocol. All functionality for generating Vuser scripts for mobile applications is now provided with the Web - HTTP/HTML protocol. For details, see Web - HTTP/HTML - Recording Methods for Mobile Applications in the LoadRunner Help Center.

Protocols supported for replay only

If a protocol has support for replay only, then you can no longer record scripts based on that protocol.

Protocol Supported for replay only
EJB (Enterprise Java Beans) From version 12.00
JavaScript Vuser From version 12.00
MMS (Media Player) From version 12.53
MMS (Multimedia messaging service) From version 12.53
Silverlight From version 12.55
VBScript Vuser From version 12.00
Web - Click and Script From version 12.00

Fully removed protocol support

There is no record or replay support for the following protocols:

Protocol Supported for replay only Not supported
DB2 CLI From version 11.00 From version 12.55
i-mode From version 11.00 From version 12.55
Informix From version 11.00 From version 12.55
PeopleSoft Enterprise From version 12.00 From version 12.55
PeopleSoft -Tuxedo From version 12.00 From version 12.55
Real From version 11.50 From version 12.55
SAP - Click & Script From version 12.53 From version 12.55
Siebel - DB2 CLI From version 11.00 From version 12.55
Siebel MSSQL -- From version 12.55
Siebel Oracle -- From version 12.55
SQL Server From version 11.50 From version 12.55
Sybase Ctlib From version 11.00 From version 12.55
Sybase Dblib From version 11.00 From version 12.55
Tuxedo From version 12.00 From version 12.55
VB Vuser -- From version 11.50
VoiceXML (VXML) From version 11.00 From version 12.55
WAP From version 11.50 From version 12.55


Protocols planned for removal in future versions

Support for the following protocols will be discontinued in upcoming versions of LoadRunner and Performance Center. We recommend that you do not use these protocols for new scripts:

Tip:  You can migrate your existing Ajax Click & Script scripts to another Web protocol such as TruClient - Web or Web - HTTP/HTML

Beta and tech preview features

This product includes limited functionality entitlements – these can be either “beta” or “tech preview” features (as indicated in the What’s New). This means that these beta or tech preview features may be undergoing further testing before their full capabilities are released. These features, including their capabilities and content, are provided on an “as is” basis. Micro Focus disclaims all other warranties. Micro Focus shall not be responsible for any loss or damage suffered by any customer as a result of their use of any beta or tech preview feature.

Micro Focus reserves the right to change or remove a beta or tech preview feature at any time, without further notice. These features, which include basic capabilities, are currently offered as embedded features accompanying the product license. In the future, Micro Focus may offer advanced capabilities for the same features at a separate cost.

Should you encounter any bugs, glitches, lack of functionality, or other problems with any beta or tech preview feature, please let us know immediately. Your help in this regard is greatly appreciated.

Send your feedback to

Additional resources

The Usage Hub enables you to view license information and usage for all HPE Software products and solutions that are installed in your environment. The Usage Hub is a central server that runs in the background. It collects, maintains, and provides a centralized view of software deployments, license assets, and the product features.

In addition, follow these links to learn more about LoadRunner and other HPE products.

Legal Notices


Certain versions of software and/or documents (“Material”) accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company.  As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company.  Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.


The only warranties for Seattle SpinCo, Inc. and its subsidiaries (“Seattle”) products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. Seattle shall not be liable for technical or editorial errors or omissions contained herein. The information contained herein is subject to change without notice.

Restricted Rights Legend

Confidential computer software. Except as specifically indicated, valid license from Seattle required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license.

Comodo Code Signing Certificate

The code signing certificate for LoadRunner was changed from Verisign to Comodo starting on January 1, 2017.

If you are installing this product on a computer with an older version of Windows, or on a computer without automatic Windows updates, the Comodo root certificate may not automatically be included as a trusted root certificate.

In such cases, we recommend manually configuring Comodo as a trusted root certificate.

For more details, see:

Copyright Notice

© Copyright 1993-2018 EntIT Software LLC

Trademark Notices

Adobe™ is a trademark of Adobe Systems Incorporated.

Microsoft® and Windows® are U.S. registered trademarks of Microsoft Corporation.

UNIX® is a registered trademark of The Open Group.

Oracle and Java are registered trademarks of Oracle and/or its affiliates.

Send documentation feedback