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

For more information, see Manage licenses.

When trying to run the LoadRunner Enterprise Configuration Wizard, it displays the error: “Failed to load object HP.Software.HPX.ConfigurationModel.Pages.PageInstaller. Would you like to continue with the configuration?"

Resolution: This is an indication that the Windows operating system is corrupted. We recommend performing a clean installation of the Windows operating system on the affected machine.

If Oracle is installed on the machine intended for the LoadRunner Enterprise Server, the IIS port will be in use by HTTPOra service. To use the machine as a LoadRunner Enterprise server, you must stop and disable the HTTPOra service, run IIS, and install the LoadRunner Enterprise server.

LoadRunner Enterprise server and host components are not FIPS complaint and cannot operate on a FIPS enabled Windows machine. For details on how to work with LoadRunner Enterprise on a FIPS enabled Windows machine, see Software Self-solve knowledge base article KM01420828.

You must update CA and TLS certificates if they were created with LoadRunner tools (Controller, MI Listener, Load Generators, Monitors Over Firewall) or if they do not contain the required extension information for the CA certificate being used. For details, see the Security - CA certificate section in the LoadRunner Known issues.

For LoadRunner Enterprise, in addition to these steps, you also need to update CA and TLS certificates for the LoadRunner Enterprise server which communicates with load generators for LAB-related operations. These certificates are located in the <LoadRunner Enterprise server installation folder>\dat\cert folder. See the above instructions for details on how to obtain the required certificates.

When uploading a script to LoadRunner Enterprise, the length of the script file name combined with the length of the LoadRunner Enterprise server installation path cannot exceed 100 characters.

• The Citrix Connection Center may prevent record and replay of Citrix ICA scripts if it is running in a different user session on the same machine.

  Resolution: Close all instances of the concenter.exe process for all users. To prevent the Citrix Connection Center from starting automatically, set the ConnectionCenter registry key to an empty value. This key can be found at:

  • For 32 bit systems: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Run

  • For 64 bit systems: HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Wind ows\CurrentVersion\Run

HTML-based Vusers using Auto Proxy configuration may influence LoadRunner Enterprise host memory usage during a large performance test run.

You cannot view the "Snapshot on Error" if a Vuser is running on a Linux load generator.

When the Vuser script is a compiled Vuser, the Controller does not send the .dll to the remote machine.

Resolution: Using VuGen, add the .dll to the list of script files and upload the script to your project.

We recommend uploading DevWeb scripts to LoadRunner Enterprise as ‘all files’. Otherwise, you should make sure the scripts include all the relevant files, such as parameters and additional JavaScript in the runtime files.

When running TruClient IE browser in Service Session using a non-interactive user, there may be issues with the browser cache and with HTML5 Local Storage (Local Storage enables Web applications to locally store data within the user's browser).

There are two possible workarounds available:

• Workaround 1 (recommended for LoadRunner and LoadRunner Enterprise users):

  You can run the browser with interactive user credentials, using one of the following solutions. Both of these solutions require a valid interactive user in the relevant domain, with permissions created by your administrator.

  • When working with LoadRunner Enterprise, the service mode issues are solved by configuring the credentials for the agent remotely, from the LoadRunner Enterprise UI. For details, see Reconfigure the LoadRunner Agent user.

  • On the load generator machine, edit the file “logon_user_config_file.cfg” located in the <LoadRunner installation directory>\launch_service\dat folder. Configure the logon type as LOGON32_LOGON_INTERACTIVE instead of LOGON32_LOGON_SERVICE, and restart the LoadRunner Agent Service.

  Workaround 2 (recommended for Application Performance Management users):

  Configure User Credentials for Services Session in the TruClient Supportability Tool. This affects only TruClient IE Vusers.

The remote host installation feature should be used for installing LoadRunner Enterprise certified installations only.

Before running the IP Wizard to define multiple IPs on a host, make sure to first add the host.

When performing an action on multiple resources (for example, checking hosts or assigning hosts to pools), you should limit the action to a maximum of 30 resources at one time.

The Docker image names which are displayed by default in the Docker Images tab in LoadRunner Enterprise Administration (Configuration > Orchestration) are misspelled, and the images only exist if they have been pulled from Docker hub.

When creating a new cloud host template, the default value of the Host Installation field is set to Windows Standalone LG. If you are working with a Linux environment image, make sure to set the Host Installation field to Unix Load Generator.

Provisioning hosts on Micro Focus Cloud may fails with the following error: "Quota exceeded for ram: Requested <amount>, but already used <amount> of <totalAmount> ram".

Resolution: Micro Focus Cloud limits the amount of RAM that can be provisioned in each region. If the RAM requirements of the hosts you attempt to provision exceed the region limit, you will receive this error. Contact Micro Focus Cloud support and verify your account limits.

Provisioning fails, and the following error appears in the Site Administration log: The supplied password must be 8-123 characters long and meet password complexity requirements.

Resolution: Run provision again and select a password that meets the operating system passwords complexity requirements.

Provisioning hosts on Micro Focus Cloud is supported only when using the default security group. The default security group must be configured with the minimum rules required.

Provisioning a load generator on Amazon EC2 Cloud, when the Amazon security group name contains spaces, results in the following error: "Invalid expression [<security group name>]. Message: literal ['xxx'] is illegal".

Resolution: Create a new security group in Amazon with no spaces.

If you create a Load Test with a monitor profile and copy it to a different project, but choose not to copy linked entities, you cannot remove the monitor profile.

To ensure the correct time range for running the performance test is displayed in the online graph, the time zone on the LoadRunner Enterprise Server and any external analysis database servers must all be synchronized.

If the Total Processor Time does not appear on the Host Monitor graph, this is due to a Microsoft limitation related to time synchronization between the client and server machines.

A Load Generator Over Firewall machine can act either as a Load Generator or as the source machine for the Network Delay monitor at a given time, but not both of them concurrently.

If you install a SAPGUI client that is logged in with a specific user, the SAPGUI may not work when logging in with a different user.

Resolution: Install the SAPGUI client with the IUSR_METRO or equivalent LoadRunner Enterprise user (LoadRunner Enterprise Identity).

• To change the default monitor settings of the Network Delay Time monitor, use ICMP instead of TCP.

• The Network Delay Time monitor shows "No Data" in the online graphs when using Windows Server 2008 R2 SP1.

  Resolution: On the Windows 2008 R2 machine:

  1. Install all the latest updates.
  2. Add support for SHA-2 signing and verification functionality. For details, see https://technet.microsoft.com/en-us/library/security/3033929.

• You might experience a degradation in online graph performance when using SiteScope monitors with a large number of measurements.

  Resolution: If possible, use less measurements in SiteScope. If the SiteScope server is also used for purposes other than performance testing, try allocating another SiteScope server specifically for performance testing with less measurements configured in it.

• When opening SiteScope from the Topology Designer window or the Performance Test Run window, most of the SiteScope options are disabled except for the options needed for configuring SiteScope monitors.

• Topology integration is not supported in Community edition for the last supported SiteScope version. To enable the integration, you must upgrade your SiteScope license. For details on upgrading your license, see the SiteScope Deployment Guide available from the Software Documentation Portal at https://docs.microfocus.com/, or contact Micro Focus MySupport.

• Starting at Google Chrome 45 (http://www.java.com/en/download/faq/chrome.xml) and Mozilla Firefox 42 (http://www.java.com/en/download/), NPAPI plugins are no longer supported (technology required for Java applets).

To see the Vusers Log in an environment where the system user is non-administrative, grant the non-administrative system user full control of the following directory on the Controller machine: %windir%\system32.

If one of the diagnostics probes is offline, LoadRunner Enterprise does not try to establish a connection to the remaining probes in the list. The performance test runs with no issues, but no diagnostic metrics are collected. Wait until the performance test starts and check if all probes were successfully connected. If they were not, stop the test, remove the problematic probe and restart the performance test.

When the URL Authorization feature is installed and enabled as part of the IIS role, the LoadRunner Enterprise pages are not rendered correctly and some functionality issues, such as uploading a script and starting a performance test, can occur.

If you configure LoadRunner Enterprise to postpone result collation to a later time, you need to configure an additional setting for Diagnostics data. Modify the server.properties file on the Diagnostics server <Diagnostics_HOME>\Server\etc directory and set distributor.offlinedelivery.preserveFiles = true.

If the LoadRunner Enterprise host cannot access the Diagnostics Server during data collation, the LoadRunner Enterprise collation for the Diagnostics metrics will fail.

When running a performance test using the Controller as the only load generator machine, LoadRunner Enterprise is unable to collate Diagnostics results.

Resolution: Avoid running Vusers on the Controller machine, or manually copy the Diagnostics .eve files from the Diagnostics Server /data/<RunID> to the <LT_Result_Folder>\j2ee_bd LoadRunner Enterprise results folder.

The results are saved for up to five days. To extend this time, Modify the webserver.properties file on the Diagnostics server <Diagnostics_HOME>\Server\etc directory and change the default facade.run_delete_delay=5d to extend the number of days.

To view Diagnostics data in Analysis, use the Analysis option to open the complete data rather than the summary data.

LoadRunner Enterprise cannot collate Collector metrics, Probe metrics, and Host metrics. This data will not appear in Analysis, but it is available online during the performance test run.

Internet Explorer 11 is a legacy browser that can be considerably slower than other modern browsers when using the LoadRunner Enterprise platform.

Recommendations:

• To avoid excessive memory usage when using LoadRunner Enterprise with an Internet Explorer browser, close the browser after logging out of LoadRunner Enterprise.
• Migrate away from Internet Explorer 11 and utilize a more modern browser for LoadRunner Enterprise. For details on other supported browsers, see the System Requirements.

There might be small discrepancies in the number of successful and unsuccessful transactions displayed in offline results (next to the bar chart), and the actual number that is displayed in Analysis and the HTML report. This is because the number in the offline results is based on data stored just before the test ended, and not the actual raw data stored on the load generator machines.

The maximum number of files that can be zipped for the collate or analysis process is limited by WinZip to 65,535. If you change the runtime logging settings to debug mode (Run-time Settings > General:Log > Extended log), it is likely, when running a performance test with a few hundred Vusers for more than an hour, that you will exceed this limit and WinZip will fail to create a zip file.

When a new user name is created using a previously deleted user name, the statistical data is combined and presented in the reports as data from one user name.

Resolution: Do not reuse previously deleted user names.

• Network Virtualization is not supported on EC2 instances type which have ENA (Elastic Network Adapter) due to a conflict with the NV Driver.

• Installation of the Network Virtualization for Linux package (NV4LG) is not currently supported on Ubuntu 18.04, due to NV Driver installation failure.

• Upgrading from Performance Center 12.6x to LoadRunner Enterprise 2020 (for LoadRunner Enterprise host only): If NV for Controller and NV for Load Generator co-exist on the machine, and you select Custom mode installation, then you are unable to modify Setup configuration settings.

  Resolution: Exit the wizard and uninstall the NV components. Then reinstall them by manually running the NV installation. See the installation section in the Network Virtualization for LoadRunner Help.

• Microsoft Internet Explorer 11.00 is not supported when working with Network Virtualization from LoadRunner Enterprise.

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

• Analysis Summary reports and NV Insights show “None” as the Virtual Location name even though no groups with this name were set in a LoadRunner Enterprise test.

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

When using an IE 10 browser on Windows 10 operating systems, help pages all open to the Help front page.

Resolution: Open the Help and search for the required information manually by using the search or contents fields, or use a different browser.

If a help link results in a 404 (page not found) error, try the following:

• On the 404 page, click Home Page to access the home page for the latest help, then select the relevant version from the version dropdown list.

• If the link was saved from a previous version, try replacing the version number in the URL with latest. For example, change:

  https://admhelp.microfocus.com/pc/en/12.60-12.63/online_help/...

  to

  https://admhelp.microfocus.com/pc/en/latest/online_help/...

• To enable multi-language support, the DB and FS servers must support Unicode. In Oracle, multi-language support is defined when installing the server.

• When working with an Oracle UTF-8 database, you can enter text in more than one non-English language.

Special characters not shown correctly in CLOB columns after upgrading to Oracle 12.2. For details, see Software Self-solve knowledge base article.

Opening and updating a project that contains characters different from those set in the ClientOSLocale or ClientOSAdvanceLocale may cause irreversible damage.

To display non-English characters, the OSLanguage needs to include the proper fonts for the language.

• The InputLanguage inserted from an external component to LoadRunner Enterprise must be the same as the ClientOSLocale and ClientOSAdvanceLocale. For example, you cannot insert a UFT script that contains Japanese characters in a client that runs on an OSLanguage with ClientOSLocale or ClientOSAdvanceLocale that is not Japanese.

• The SiteAdminDBCollation and ProjectDBCollation must be set to the same language as the data insert. For example, inserting Japanese characters in a Korean collation is not supported.

The Spell Checker tool is available only in English.

Due to a problem in the JDBC driver’s specific version, using Chinese and Japanese collation in MS-SQL may cause an error while executing some actions.

On Hebrew locale client machines, to ensure that memo fields (for example, Description, Comments, Rich Text) are displayed properly, configure the settings in the Control Panel > Regional and Language Options window. Set Languages For Non-Unicode Programs (Administrative tab) and Current Format (Format tab) to Hebrew.

Non-English national characters are not supported in project names.

Resolution: Use English characters in project names.

Non-English Cyrillic URLs are not supported when creating noise scripts.

Resolution: Use English characters when creating noise script URLs.

The following characters are not supported in Microsoft SQL Japanese_CI_AS collation : U+30A0, U+30F7, U+30F8, U+30F9, U+30FA, U+30FB and U+30FF.

Resolution: Enable the Use Unicode option when using Microsoft SQL Server as a project database.

When working with a localized version of LoadRunner Enterprise, you must install Arial Unicode MS - version 1.00 or later on your LoadRunner Enterprise server.

A localized version of the Web Client is available only in Japanese.

To support Unicode characters when exporting Trend reports to PDF, install Arial Unicode MS (ARIALUNI.TTF font) on the LoadRunner Enterprise Server.

When running system health on a LoadRunner Enterprise machine, the SiteScope health check might fail when parsing the SiteScope version number. This problem occurs on localized machines that treat the decimal point as a comma.

Resolution: Ignore the error.

Global Search is not available in a localized version.