Share this page

# Known issues

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.

In this topic:

## Installation and upgrade

This section includes the following installation and upgrade issues:

Licenses | 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.
Configuration Wizard | 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 you update the script to the new path (<LoadRunner installation directory>\LREConfiguratorWizard instead of <LoadRunner installation directory>\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.
Upgrade | 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).
UAC enabled | Unable to install LoadRunner Enterprise server with UAC enabled on top of LoadRunner Enterprise versions earlier than 2023. Resolution: Disable UAC during the upgrade process, and enable it after LoadRunner Enterprise server installation is complete.
Oracle | 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 disable the HTTPOra service, run IIS, and install the LoadRunner Enterprise server.
FIPS Compliant | 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.
Disk space | 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.

Back to top

## Vuser scripts

This section includes the following Vuser script issues:

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. The only files that should be uploaded are: 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
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.
Running TruClient as a service (Relevant for LRE 2023 only; LRE 2023 R1 does not support running tests that include TruClient IE scripts) | 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 Professional and LoadRunner Enterprise users): 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 service session. For details, see TruClient Supportability Tool in the Virtual User Generator Help Center. This affects only TruClient IE Vusers.
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 Virtual User Generator Help Center.

Back to top

## Hosts

This section includes the following host issues:

Remote host installation | The Remote Installation feature is unavailable in the 2023 and 2023 R1 releases and was removed from the user interface.
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), you should limit the action to a maximum of 30 resources at one time.
Check host status | The Check Host Status grid is empty when checking host status on a OneLG installation.

Back to top

## Cloud load generators

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 `OneLG` in LoadRunner Enterprise. If you are working with a Linux environment image, make sure to set the Host Installation field to `Unix Load Generator`.
Provisioning fails - invalid password | 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.
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: `"Invalid expression [<security group name>]. Message: literal ['xxx'] is illegal"`. Resolution: Create a new security group in Amazon with no spaces.

Back to top

## Online monitoring

This section includes the following online monitoring issues:

Monitor profile | 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.
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 | 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.
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.
SAPGUI client | 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 | 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: Install all the latest updates. Add support for SHA-2 signing and verification functionality. Refer to the Microsoft documentation for more details.
SiteScope monitor | 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. 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. Starting at Google Chrome 45 and Mozilla Firefox 42, NPAPI plugins are no longer supported (technology required for Java applets).

Back to top

## Performance test run

This section includes the following performance test run issues:

Vusers log | To view the Vusers Log, a non-administrative system user must be granted full control of the %windir%\system32 directory on the Controller machine.
URL Authorization | 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: Log in to the LoadRunner Enterprise server and start Server Manager. On Server Manager, go to Roles > Web Server (IIS), and uninstall URL Authorization. Removing this feature does not impact IIS or LoadRunner Enterprise.
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 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. 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. 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. Navigate 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>'` 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. 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. Run a test and check for Active Reservation/Timeslot ID in the Hosts grid. The problem should be resolved.

Back to top

## Network Virtualization (NV)

This section includes the following Network Virtualization issues:

Installation | As of LoadRunner Enterprise 2023, Network Virtualization is no longer supported on Linux load generators. If you attempt to download Network Virtualization installation files from the Internet or an FTP site, the files are blocked to protect the computer from untrusted files and the following message is displayed: Resolution: Before installing NV, unblock the files as follows: Right-click one of the NV installation executable files located in <NV installation path>\Additional Components\Network Virtualization, and select Properties. If there is an Unblock checkbox in the General tab, select it and click OK. Verify that the Unblock checkbox is gone. Repeat for each executable file in the Network Virtualization folder.
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.

Back to top

## Multi-tenant environments

This section includes the following multi-tenant environment issues:

Support | The following are not supported in a multi-tenant environment: Docker Swarm, Kubernetes Dockerized load generators InfluxDB Remote Installations

Back to top

## General

This section includes the following general issues:

Browser | 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, you should use different browsers types or open the new browser window in incognito mode.
Site Configuration | 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 you update the password saved in the browser, or open the browser in incognito mode instead.
HTML Report | The HTML Report is missing the following SLA criteria: Hits per second, Transactions per second, and Transactions per second (passed).
LoadRunner Backend Service | The LoadRunner Backend Service does not start automatically after a Windows reboot when Automatic startup type is configured. Resolution: Change the startup type for the LoadRunner Backend Service to Automatic (Delayed Start).
Monitor Over Firewall | Avoid using empty spaces in Lab location names since it can cause problems when using load generators over a firewall.
Offline results | 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.
REST API | Project names, domain names, and any other resource that is passed as a query parameter in a public API cannot contain Microsoft Windows reserved words, such as COM1-9, LPT1-9, AUX, PRT, NUL, and CON.
Result Collation | 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.
Log Collator | 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.
Usage reports | 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.
Scaling and zoom | Changing the display settings, to reset the display scale and zoom, is not supported for any LoadRunner Enterprise or LoadRunner Professional components.

Back to top

## Documentation

This section includes the following documentation issues:

Help link gives 404 | 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/...

Back to top

## Internationalization limitations

This section includes the following internationalization issues:

Unicode | 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.
Oracle 12.2 database | Special characters not displayed 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.
Fonts | To display non-English characters, the OSLanguage needs to include the proper fonts for the language.
Component language must match | 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.
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.
Reports | Non-Latin characters are not supported in exported PDF reports. This includes the project name, user name, machine name, and load generator name. Resolution: When using a Korean, Japanese, or Chinese interface, log in to LoadRunner Enterprise using the English interface, and download the report in English instead.
Project names | 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.
REST API | 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.

Back to top

## Localization limitations

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, install the Arial Unicode MS font (ArialUnicodeMS.TTF) to the <installation root>\bin\externalFonts\ folder on the LoadRunner Enterprise Server.
System health | 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.

Back to top

See also:

- Unsupported and deprecated features
- Known issues in LoadRunner Professional (LoadRunner Enterprise uses various LoadRunner Professional tools)

https://admhelp.microfocus.com LoadRunner Enterprise 8942
Tips to improve your search results... LoadRunner Enterprise Help Center LoadRunner Enterprise Help LR Enterprise Help 2023-2023 R1 All View Local Help Center View Online Help Center back Go back in browser history forward Go forward in browser history Remove search highlights next topic Go to next topic previous topic Go to previous topic Print the current topic Version: