When upgrading from Performance Center 12.6x or LoadRunner Enterprise 2020 or later, you need to request and upload new licenses to work with the upgraded LoadRunner Enterprise version. For details, see Set license keys.

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.

• The location of the Configuration wizard executable was changed in LoadRunner Enterprise 2023. If you are installing LoadRunner Enterprise silently and the silent installation script targets the configuration wizard (instead of the MSI installer), make sure that you update the script to the new path (<LRE_installdir>\LREConfiguratorWizard instead of <LRE_installdir>\bin).

• When trying to run the LoadRunner Enterprise Configuration wizard, it displays the error: “Failed to load object "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.

• IUSR_METRO user is removed from LoadRunner Enterprise hosts on upgrade.

  Resolution: Run Reconfigure Host for all hosts that were upgraded, or remove and add the hosts back to the LoadRunner Enterprise server (this adds the user back to the hosts).

• When upgrading from LoadRunner Enterprise 2022, or if you ran LoadRunner Enterprise 2022 in the past, the site administrator upgrade might fail at the end of the Configuration wizard with the following error: "Unable to materialize entity instance of type 'Session".

  Resolution: Open the Site Admin schema, Sessions table, and check that the SSN_TYPE column does not contain records with no data. If it does:

  1. Run the following SQL query to delete these records:

     Copy code

     DELETE from Sessions where SSN_TYPE = "

  2. Run the LoadRunner Enterprise server configuration wizard again.

If Oracle is installed on the machine intended for the LoadRunner Enterprise Server, the IIS port is used by the HTTPOra service.

Resolution: To use the machine as a LoadRunner Enterprise server, you must stop and deactivate the HTTPOra service, run IIS, and install the LoadRunner Enterprise server.

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 Professional 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 <LRE_server_installdir>\dat\cert folder. See the above instructions for details on how to obtain the required certificates.

The \scripts, \orchidtmp\Repository, orchidtmp\transferfiles, and \orchidtmp\TempFiles folders in the LoadRunner Enterprise server installation directory are cleaned by a background job which runs daily, and cleans up folders and files that are more than two days old. The run frequency and file "age" are not configurable.

Unable to upload script files

Unable to upload a JMeter, Gatling, Silk, or Selenium script to LoadRunner Enterprise that you previously downloaded, unless you first delete all the extra files from the script folder. Make sure you upload the following file types only:

• For JMeter: .jmx, <script name>_UserData.txt

• For Gatling: .scala

• For Silk: .xml, .ltp, .bdf

• For Selenium: .java

Script file name

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.

Citrix ICA scripts

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

• If the agent is running as a service, and the load generator is running on a Windows operating system, Windows limits the number of processes that can be opened according to the desktop heap size defined in the registry. If the heap size is insufficient, no more java processes can be opened, and the Vusers will fail.

  Resolution: Change the registry value that sets the heap size on windows machines. This is the third value defined under key: HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Session Manager\SubSystems\Windows\SharedSection. Usually, this value is set to 768. You can increase it to a maximum of 8192.

• Java includes parameters to define the maximum metaspace/heap size, and the commit size (reserved memory), that are used for Java processes. You can view the values for these parameters by running the command: java -XX:+PrintFlagsFinal

  To avoid issues, note the following:

  • The maximum metaspace size is calculated considering the actual memory capacity of the machine. For example, for Java 1.8, the size is calculated as 25% of the possible maximum value. We recommend that you increase the calculated value for better performance.

  • The commit size is greater than the memory that is used, and it scales with the maximum heap size (Xmx). We recommend to decrease the commit value, so that more Java processes can be opened on the machine without running out of memory.

  You can change the maximum metaspace and commit size values by adding arguments to the Java command line. In the Runtime Settings, add this value: -XX:MaxMetaspaceSize=34359214080 -Xms10m -Xmx110m

  The maximum value (Xmx) should be determined after running the script and looking at the Java memory consumption.

HTML-based Vusers

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

Snapshot on Error

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

Compiled Vuser

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.

TruClient Browser for TruClient Native Mobile protocol is no longer automatically installed with LoadRunner Enterprise.

Resolution: If you are using this protocol to run TruClient scripts in LoadRunner Enterprise, you must install it manually on all your load generator machines. For details, see Install TruClient Browser for TruClient Native Mobile protocol in the Virtual User Generator Help Center.

IP Wizard

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

Performing action on multiple resources

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

Check host status

When creating a new cloud host template, the default value of Host Installation is set to OneLG in LoadRunner Enterprise. If you are working with a Linux environment image, make sure to set Host Installation to Unix Load Generator.

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 provisioning again and select a password that meets the operating system passwords complexity requirements.

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.

You cannot delete a monitor profile when creating a test with the profile and coping it to a different project, without coping its linked entities.

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

The Total Processor Time is not always displayed 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, but not for both at the same time.

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

Resolution: Install the SAPGUI client with 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. Refer to the Microsoft documentation for more details.

• 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 non-performance testing purposes, try allocating another SiteScope server specifically for performance testing with less measurements configured in it.

• Starting at Google Chrome 45 and Mozilla Firefox 42, NPAPI plug-ins are no longer supported (technology required for Java applets).

To view the Vusers Log, a non-administrative system user must be granted full control of the %windir%\system32 directory on the Controller machine.

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. This can be caused by working with an unsupported IIS configuration.

Resolution: Make sure URL Authorization is not installed on IIS. To uninstall URL Authorization:

1. Log in to the LoadRunner Enterprise server and start Server Manager.

2. On Server Manager, go to Roles > Web Server (IIS), and uninstall URL Authorization. Removing this feature does not impact IIS or LoadRunner Enterprise.

When working with a PostgreSQL database server, after installing LoadRunner Enterprise or changing the time zone on the LoadRunner Enterprise server or database, the Active Reservation/Timeslot ID column in the Hosts grid in both LoadRunner Enterprise and LoadRunner Enterprise Administration are empty when running a test. This occurs when the time zone of the LoadRunner Enterprise server differs to the time zone set on the operating system of the database server.

Resolution: Align the time zone on the operating system with the time zone in the postgresql.conf file.

1. On the database server machine, open pgAdmin. Open lre_<tenant-name>_tenant_db or any LoadRunner Enterprise related DB file.

   Open a new script and run:

   SELECT now()

   Check if there are any differences between the time displayed in the query result and the time of the operating system.

2. Check the time zone set in PostgreSQL by running:

   SHOW timezone

   Check the time zone set on the operating system. They are probably different time zones.

3. Go to <postgresql-install-dir>/<version-of-pg>/data and open the postgresql.conf file. Search for the "timezone" section. You should find the following line:

   timezone = '<Continent>/<City>'

4. Go back to pgAdmin and run the following:

   SELECT name, abbrev, utc_offset, is_dst FROM pg_timezone_names ORDER BY utc_offset;

   This should give you a table of all available values that you could put in the postgresql.conf file. Select the name that matches the operating system time zone. Replace the value in postgresql.conf with the chosen value, and save the file.

5. In pgAdmin run:

   SELECT pg_reload_conf();

   Followed by:

   SHOW timezone

   Followed by:

   SELECT now()

   It should now display the correct (OS) time zone and time.

6. Run a test and check for Active Reservation/Timeslot ID in the Hosts grid.

The following are not supported in a multi-tenant environment:

• Docker Kubernetes

• Dockerized load generators

• InfluxDB

• For all versions: In order to use LDAP for authentication, the LoadRunner Enterprise machine must have access to the following controls: 1.2.840.113556.1.4.319 and 1.2.840.113556.1.4.1340.

• If you perform an upgrade from a version prior to 24.1 and encounter an issue with LDAP authentication, perform the workaround described in the Software Self-solve knowledge base article KM000029035.

• IPv6 is not supported on Dockerized load generators.

• Network Virtualization emulation is not supported for IPv6 network traffic.

For a list of monitors that support IPv6, see the section on IPv6 support in the Support Matrix.

The following features, protocols, integrations, and components that work with LoadRunner Enterprise are not FIPS compliant:

• Alerts

• Web Services protocol

• .NET protocol

• SharpDevelop IDE (in VuGen and LRStudioAPI)

• Network Virtualization

• LoadRunner Analysis

Values are missing in the filter dropdown of the maintenance timeslot Grid view if no results for that value are retrieved from the first page of the database.

Using LoadRunner Enterprise and LoadRunner Enterprise Administration in multiple tabs in the same browser is not supported, regardless of whether you are logged on with the same or a different user. For example, if you open LoadRunner Enterprise in one tab, you cannot log on to LoadRunner Enterprise Administration in another tab in the browser.

Resolution: If you need to work in multiple instances of LoadRunner Enterprise, use different browsers types or open the new browser window in incognito mode.

A network password error is encountered when switching between SSO and LDAP authentication if the user password is saved in the browser.

Resolution: Make sure that you update the password saved in the browser, or open the browser in incognito mode instead.

The LoadRunner Backend Service does not start automatically after a Windows restart when Automatic startup type is configured.

Resolution: Change the startup type for the LoadRunner Backend Service to Automatic (Delayed Start).

There might be small discrepancies in the number of successful and unsuccessful transactions displayed in offline results), 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 when running a performance test with a few hundred Vusers for more than an hour, the limit is likely to be exceeded and WinZip won't be able to create a zip file.

After launching the Log Collator utility from the LoadRunner Enterprise server, the connection to the LoadRunner Enterprise server fails, and cannot display all available hosts and servers.

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

Resolution: Do not reuse previously deleted user names.

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/lre/en/2022/online_help/...

  to

  https://admhelp.microfocus.com/lre/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 displayed 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 One 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.

Non-Latin characters are not supported in exported PDF reports. This includes the project name, user name, machine name, and load generator name. As a result, when using a Korean, Japanese, or Chinese interface, the PDF report content is downloaded in English.

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.

To support Unicode characters when exporting Trend reports to PDF, install the Arial Unicode MS font (ArialUnicodeMS.TTF) to the <installdir>\bin\externalFonts\ folder 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 occurs on localized machines that treat the decimal point as a comma.

Resolution: Ignore the error.