This section displays notes and limitations for working with LoadRunner Enterprise. Additional known issues and workarounds are included in the relevant sections of the help center.
This section includes the following installation and upgrade issues:
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,
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.
|Configuration Wizard error||
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 the HTTPOra service.
Resolution: 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 compliant 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.
|Security - CA certificate||
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 installation folder>\dat\cert folder. See the above instructions for details on how to obtain the required certificates.
|Missing dll||If you encounter an error that the api-ms-win-crt-string-l1-1-0.dll is missing during the LoadRunner Enterprise Server installation or configuration process, you should restart the LoadRunner Enterprise server.|
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.
This section includes the following Vuser script issues:
|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:
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.
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.
Java Vusers are not supported over the firewall.
|Running TruClient as a service||
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:
|TruClient Native Mobile protocol||
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 TruClient Help Center.
This section includes the following host issues:
|Remote host installation||
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 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), you should limit the action to a maximum of 30 resources at one time.
This section includes the following cloud load generator issues:
|Cloud host template
When creating a new cloud host template, the default value of the Host Installation field is set to
|Provisioning fails - invalid password||
Provisioning fails, and the following error appears in the Site Administration log:
Resolution: Run provisioning again and select a password that meets the operating system passwords complexity requirements.
|Amazon security group name contains spaces||
Provisioning a load generator on Amazon EC2 Cloud, when the Amazon security group name contains spaces, results in the following error:
Resolution: Create a new security group in Amazon with no spaces.
This section includes the following online monitoring issues:
If you create a test with a monitor profile and copy it to a different project, but don't copy its linked entities, you cannot delete the monitor profile.
|Time range displayed||
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.
|Total Processor Time||
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.
|Load Generator Over Firewall machine||
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 concurrently.
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).
|Network Delay Time monitor||
This section includes the following performance test run issues:
To be able 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.
|Active timeslot ID missing when running a test||
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 you run 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.
This section includes the following Network Virtualization issues:
|Upgrading hosts from Performance Center 12.6x||
When upgrading hosts from Performance Center 12.6x to LoadRunner Enterprise 2020 or later, if NV for Controller and NV for Load Generator co-exist on the machine and you select Custom mode installation, 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.
This section includes the following multi-tenant environment issues:
The following are not supported in a multi-tenant environment:
This section includes the following general issues:
This section includes the following documentation issues:
|IE 10 on Windows 10||
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.
|Help link gives 404||
If a help link results in a 404 (page not found) error, try the following:
This section includes the following internationalization issues:
|Oracle 12.2 database||
Special characters not shown correctly in CLOB columns after upgrading to Oracle 12.2. For details, see Software Self-solve knowledge base article.
|Different characters in project||
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.
|Component language must match||
|Character limit in LoadRunner Enterprise edit box||The number of double-byte characters you can enter in a LoadRunner Enterprise edit box may be more limited than the number of characters specified in the relevant error messages. The number of characters that can actually be used depends on the database definitions and the character set collation that is being used. For example, one character can occupy 3 bytes when using Japanese characters with a database that is defined to work with UTF-8.|
|LDAP authentication||Non-English character sets are not supported when using LDAP authentication.|
Non-English national characters are not supported in project names.
Resolution: Use English characters in project names.
|Non-English Cyrillic URLs||
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.
This section includes the following localization issues:
|SSO authentication||Multilingual user interface is not supported when logging in to LoadRunner Enterprise Administration using SSO authentication.|
|Localized user name||Localized user names are not supported in LoadRunner Enterprise 2020 or later versions.|
|Arial Unicode MS||
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.
|Exporting Trend reports to PDF||
To support Unicode characters when exporting Trend reports to PDF:
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.