The installation process, for all components, requires a full administrator account (root account for Linux systems) for all operating systems.

After installation, all of the LoadRunner Professional applications and components can run under a standard user account (an administrator account is not required), with UAC and DEP enabled.

When upgrading to version 2020, you need to replace your current license to work with the upgraded LoadRunner Professional installation. If you are using the Community license, it is automatically replaced during LoadRunner Professional installation. For any other license, contact support to obtain a valid, compatible license.

For more information, see Install LoadRunner Professional licenses.

Virtual environments

The architectures provided by virtualization vendors are rapidly evolving. LoadRunner Professional 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 Professional-approved hardware requirements.

If you follow the LoadRunner Professional system requirements and support matrix to create the virtual machine, LoadRunner Professional 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.

From version 12.60, LoadRunner Professional uses an updated version of OpenSSL, which enforces additional constraints for secure communication.

OpenSSL (from 1.1.x) requires that the basic constraints for a CA certificate include a confirmation that the certificate is a CA certificate.

Upgrade: If you are upgrading from a version earlier than 12.60, and your CA certificate was created in an earlier LoadRunner version using any of the LoadRunner tools, you can no longer use these certificates because they do not include the required constraints. Use the LoadRunner Professional tools to create and install a new CA certificate and new TLS certificates on each LoadRunner Professional machine. For details, see Secure Communication with TLS (SSL).

Organization's CA: If your CA certificate is provided by your organization, verify that the certificate includes the constraints described above. If the required constraints are not defined, your IT department should provide updated CA and TLS certificates to install on the LoadRunner Professional machines.

To verify:

Check that the constraint is defined for the CA certificate in the Basic Constraints extension, for example, Subject Type=CA or CA:TRUE (the constraint format varies, depending on how the certificate was accessed).

• On Windows: Double-click the CA certificate and select the Details tab. Select Extensions only from the Show list, then select Basic Constraints and check that the constraint is defined in the properties area.
• On Linux: Use the following command to view certificate information: openssl x509 -in <CA-filename> -noout -text.

Virtual Table Server (VTS) upgrade

• LoadRunner Professional 2020 SP1:

  • Before upgrading VTS to 2020 SP1, export the VTS data into a CSV file; after installation, import the data into VTS. For details, see Install VTS.
  • After upgrading VTS to 2020 SP1, the Refresh button on the VTS toolbar may display an incorrect number for number of events on the server.
• To upgrade VTS, first uninstall the version you have, then reinstall the latest version from the Additional Components folder.

• The default data path for VTS has been updated to C:\ProgramData\Micro Focus\VTS\db\data. To continue using your current data path:

  • When prompted during the installation, redirect the data path to your current data path

  • After installation, update the dbPath value in the VTS configuration file. Then restart VTS service.

Visual C++ installation

Visual C++ 2013 Redistributable is no longer a prerequisite for LoadRunner Professional. Note that when using the Visual Studio 2013 IDE add-in, Visual C++ 2013 Redistributable is automatically installed when installing the IDE.

Coexistence with UFT family

• We recommend that you do not install LoadRunner Professional and UFT Developer (formerly called 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 Professional to malfunction.

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

• If you install or uninstall LoadRunner Professional on a machine where UFT One (formerly called 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 Professional and UFT One 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 Professional and UFT One, on which UFT One was installed after LoadRunner Professional, may not allow the recording of certain protocols.

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

• If you install UFT One 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 One, restart the load generator agent using the Agent Configuration utility, or alternatively reboot the machine.

Uninstall

• If you have multiple LoadRunner Professional 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.

• When uninstalling a load generator on a Linux machine, the uninstall process may fail and you may get an error message saying "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.

Default browser

• 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.

Recording on Microsoft Edge browser is not supported for WinSock.

Publishing a container port fails on Windows 10 1903. As a result, Dockerized load generators are not supported when using Windows 10 1903 edition. (Recommended OS: Windows Server 2019, build 17763)

When running the License Utility with UAC enabled, LoadRunner Professional prompts you for administrator credentials.

Resolution: Run the utility as administrator.

On a Window Server operating system when recording Web protocol scripts, or recording and replaying TruClient - Web scripts, it is recommended to disable Internet Explorer Enhanced Security Configuration (IE ESC).

Resolution: In Windows 2012 R2, 2016, 2019, select Server Manager > Local Server > Internet Explorer Enhanced Security Configuration.

When recording a Web-based protocol script, the recording may fail in certain installations, if Data Execution Prevention (DEP) is enabled.

Resolution: Disable DEP on your VuGen machine. For details, see Record a Vuser Script.

When using Visual Studio and add-ins to create C# and VB .NET scripts, Visual Studio creates .NET assemblies that need to be registered in the system before their run. Registration of the .NET assembly requires administrative permissions.

Resolution: Enable UAC and register the .NET assembly before running the test using one of these methods:

• Run Visual Studio "As Administrator" and provide administrative credentials when prompted. In Project Settings, ensure that the Register for COM interop option is set (Project > Properties > Build > Register for COM interop). Visual Studio will automatically register the test DLL as a .NET assembly every time it builds the project.

• Run Visual Studio without administrative permissions, and manually register the test DLL after it is built. To do so, run Windows Console with administrative permissions and run the following command: %WINDIR%\Microsoft.NET\Framework\v4.0.30319\RegAsm.exe <TargetDLLwithPath> /codebase (ignore the warning issued when you run this command).

  For example, you might replace <TargetDLLwithPath> with c:\users\qatest\documents\visual studio 2015\Projects\LoadRunnerUser1\LoadRunnerUser1\LoadRunnerUser1.dll. You do not need to register the DLL after every build. It is enough to register it once after making changes in the COM interfaces defined in the DLL.

The IP Wizard does not function for a Limited user.

Resolution: Run the IP Wizard with administrator permissions. The IP Wizard uses raw sockets to communicate with remote machines. Therefore, administrative privileges are required for opening and using raw sockets in socket-based communication. For more information, see http://msdn.microsoft.com/en-us/library/windows/desktop/ms740548%28v=vs.85%29.aspx. Alternatively, you can set the IP Wizard settings locally on the target machine.

The network settings for load generators on Linux machines cannot be configured by a standard (non-administrator) user account.

Resolution: When working on a Linux operating system, run lr_agent_settings with administrator permissions.

If you open a Micro Focus site in the embedded browser and the site is not included in the trusted sites list, you will be prompted to add the site to the trusted site list. After adding the site, you may receive a Web site scripting error.

Resolution: Close the error and continue working as you normally would.

• SSL2 is no longer supported.

• When recording a script, some applications may be unable to connect to a server using SSL. Errors such as "Invalid certificate" and "SSL Handshake Failed" may appear. This is because VuGen now uses SHA-256-signed certificates for recording of SSL-encrypted communication instead of the older SHA-1-signed certificates.

  Resolution: Instruct VuGen to use SHA-1-signed certificates, as follows:

  1. Add the following lines to <LoadRunner Professional root>\config\vugen.ini:

     • [WebRecorder]
     • ProxyCertificateHash=sha1

  2. Delete the following files from <LoadRunner Professional root>\bin\certs\:

     • wplusCA_Expiration_2022.crt
     • wplusCAOnly_Expiration_2022.crt
     • wplusCert_Expiration_2022.crt
  3. Restart VuGen and record the application again.

• When working in VuGen with a DevWeb script, components such as Recording Options, Parameters dialog, Snapshots Viewer, or the script uploader to LoadRunner Enterprise, may not be able to download the content and hang.

  Resolution: Change the Local Area Network (LAN) proxy server settings on your machine: If you have set up your machine to Use a proxy server for your LAN, make sure the option to Bypass proxy server for local addresses is also selected.

• In some cases, when you use the LoadRunner Professional proxy to record a local application, the proxy settings are not automatically restored to their original values after the recording session. This can prevent your computer from accessing local and external Internet sites.

  Resolution: In your browser, reset the proxy settings manually.

• When you run a Java protocol script, the replay status may be Script Not Run and some errors may appear in the mdrv.log file. However, due to Java internal architecture, these errors may not be included in the VuGen Output and Errors panes. This occurs when VuGen fails to initialize a Java Vuser, and JVM then terminates the replay process.

  Resolution: Look for errors directly in the mdrv.log file (you can find this in the script’s folder). If the entry in the log is due to a memory-related issue, try using different memory options for Java in the runtime settings.

• Java-based technologies are not yet supported by Microsoft Edge. Therefore, we do not recommend selecting this browser emulation for the replay of Java-based protocols (Flex, Java over HTTP, Oracle NCA).

• Web Page Diagnostics are not supported for scripts using HTTP/2 protocol. Disable Web Page Diagnostics in Controller > Diagnostics > Configuration > Diagnostics Distribution dialog box.
• Uploading a buffer (request body) larger than 64 KB is not supported for scripts using HTTP/2 protocol.

Runtime errors generated during the replay of VBScript scripts may not be handled properly. It is recommended that you port existing VBScript scripts to C.

Possible resolution: Enable the Continue on Error option in the Runtime settings.

When you stop a named VTS instance, the instance may continue to run until you restart the VTS Windows service, which will block you from creating an instance with the same name or port.

Resolution: Restart the VTSService Windows service. For example, use the “net stop vtsservice” to stop the service, and “net start vtsservice” to restart it.

Webtrace is not supported with -proto tcp and -proto udp in the following Linux environments: RHEL 7, OEL 7.

When using the WinInet replay engine, you may encounter the following error: "HttpSendRequest" failed, Windows error code=12002.
This HttpSendRequest timeout occurs when a transaction takes more than 30 seconds (default timeout setting) to connect to the server.

Resolution: Change the default timeout setting for the WinInet replay engine. In the Registry Editor, open HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Internet Settings, and change the default time (30 seconds) to 180 seconds:

"SendTimeOut"=dword:0002bf20

"ReceiveTimeOut"=dword:0002bf20

When using the Import SOAP option to generate API web_services_call from a SOAP file, it is expected that the majority of the generated cases will be web_services_call.

However, the actual results are mainly soap_request, and very few cases of web_services_call.

• When you start a scenario, the first batch of Vusers go directly from pending to stopped. All other Vusers run as expected.

• When you stop a scenario, all Vusers are stopped, and the Start Scenario button is enabled for 1 second then returns to disabled, and stays disabled.

  Resolution: Delete the first Vuser, the Start Scenario button then reverts to enabled.

When using the SiteScope monitor, you cannot change the counters already saved with the scenario.

Resolution: Remove all existing SiteScope counters, close the dialog box and re-add them.

• The LoadRunner Professional Setup wizard prompts you to install Network Virtualization at the conclusion of the installation. If you did not install the Network Virtualization component as part of the LoadRunner Professional installation, you can run the Network Virtualization installation manually at any time.
• When installing Network Virtualization on Windows in custom mode, you must manually reboot the machine at the end of installation.

Network Virtualization usage is included with the LoadRunner Professional protocol licenses; network emulation and NV Insights do not require any additional license purchase.

• Network Virtualization emulation in Linux works only in Per group mode.
• The NV Insights report is not supported on Linux.

Analysis Summary reports and NV Insights show None as the Virtual Location name even though no groups with this name were defined in a LoadRunner Professional scenario.

Resolution: See Software Self-solve knowledge base article KM03407056.

If a Service Virtualization server uses credentials for both SSL and monitors, then the Service Virtualization project cannot be correctly imported to a scenario.

Resolution: Configure the Service Virtualization server to use credentials only for SSL.

If you have a slow connection from VuGen or Analysis to ALM, this may be because the VuGen or Analysis machine does not have access to the WAN, and so cannot verify the digital signature of the relevant files.  

Resolution: Download and import the certificates from https://support.globalsign.com/customer/portal/articles/1426602-globalsign-root-certificates using certmgr MMC until the issue is resolved (you might not need to import all the certificates).

If you install a language pack after you have already generated an Analysis session, you will not be able to open the session file (.lra). You can only open it on a machine with the same regional settings as the machine upon which it was generated. You can, however, open the raw results, the .lrr file.

On non-English operating systems, several components may contain untranslated items, such as the Print Preview page in VuGen, log files, and installation screens.

LoadRunner Professional cannot record a Vuser script for certain protocols if the LoadRunner Professional installation is on a Chinese operating system, and the installation path contains Chinese characters.

Path names cannot be in multi-byte format.

When LoadRunner Professional is installed on a Windows Server operating system, Internet Explorer Enhanced Security Configuration (IE ESC) must be disabled in order to view Help Center content. It is enabled by default.

Resolution: In Windows 2012 R2, 2016, 2019, select Server Manager > Local Server > Internet Explorer Enhanced Security Configuration.

On certain machines with high level security settings, you need to trust the domain (admhelp.microfocus.com/lr, admhelp.microfocus.com/vugen, admhelp.microfocus.com/tc, admhelp.microfocus.com/pc) in order to view the Help Center.

Resolution: Open the Help Center in IE, and accept the site as a trusted domain. Then you will be able to use the context sensitive and menu help from the product.

On Windows 8.1 and later, disabling UAC may block Acrobat Reader from opening PDF files. Follow the Windows Help instructions to enable UAC and trust Acrobat.

When opening the help locally in a Chrome browser, you cannot hide the message banner at the bottom of the screen. Clicking the Got it! button does not remove it.