Troubleshoot protocol issues

This section describes troubleshooting and limitations for TruClient protocols.

TruClient for Chromium

  • When accessing HTTP/2 web pages in Chromium, the replay log displays HTTP/1.1 in the HTTP response header.

  • The Minimum supported secure protocol setting in TruClient General Settings > Browser Settings and VuGen Runtime Settings > Load Section > Browser > SSL is not supported. TruClient Chromium always chooses the most secure protocol supported by both Chromium and the web server under test.

  • Chromium cannot record or replay inside dynamic iframes.

  • Global variable cannot be used in steps in Chromium.

    For example, this does not work:

    Step 1: Evaluate JavaScript code Global.myserver = "";

    Step 2: Navigate to Global.myserver

Back to top

TruClient for IE

  • When accessing HTTP/2 web pages in IE, the replay log displays HTTP/1.1 in the HTTP response header.

  • If you are running TruClient on a Windows Server machine, you must turn off IE Enhanced Security by selecting Server Manager > Configure IE ESC to record and replay scripts on your machine.

  • If you have trouble opening TruClient IE, you may need to disable User Account Controls (UAC) completely. Disable UAC from the Control Panel and also set the EnableLUA registry key to 0.

    The registry path for EnableLUA is HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System\EnableLUA

  • If you recorded <Click link> + Shift in your script, it does not activate a new browser tab during replay.
  • If you have recorded a script in TruClient Browser or Chromium that includes a step to open a second browser window, the script will fail on that step if you replay it in IE.

    To replay the script successfully in IE, add an If Browser step with a clause to activate a tab for the IE browser.

    The example below illustrates this implementation of the If Browser step.

  • If all steps are not correctly generated after recording a script, the problem may be due to the Windows Component > Internet Explorer Enhanced Security Configuration.

    Remove Internet Explorer Enhanced Security Configuration by selecting Control Panel > Add or Remove Programs > Add or Remove Windows Components and rerecord your script.

  • If Nvidia shim drivers are installed, TruClient IE might behave unexpectedly.

    • Ensure that Nvd3d9wrap.dll is not loaded with TruClient IE using third—party tools such as process explorer by SysInternalsl Nvd3d9wrap.dll. If Nvd3d9wrap.dll is installed, either uninstall the driver or rename the file and restart TruClient IE.
    • After the uninstall is completed, remove all dlls named nvinit.dll from the following registries:

      [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Windows\AppInit_DLLs]

      [HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Windows NT\CurrentVersion\Windows\AppInit_DLLs]

  • window.location cannot be used with Internet Explorer. Use document.URL instead.
  • Flash, Silverlight, and ActiveX are not supported

    User actions on UI elements that are based on Flash, Silverlight, ActiveX in general, and Java applets technologies are currently not recorded and replayed.

  • McAfee Antivirus causes Vusers to stop running in Load Mode.

    Newer versions of McAfee Antivirus may cause network hook collision with the TruClient for IE protocol. You may experience unexpected behavior during load. For example, some of your Vusers may stop running. As a result, an error message appears in the Controller > Scenario Status > Errors pane and the Vuser status displays as Failed.

    To resolve, add the TcWebIELauncher.exe to the McAfee exclusion list.

  • To support TruClient recording and replaying in iframe, the iframe must have the "allow-scripts" sandbox attribute. This attribute is required to enable TruClient to inject code to run inside AUT pages. The "allow-scripts" attribute exists in most iframe pages.

    Here are some examples:

    Injected code runs in iframe:

    <iframe src="demo_iframe_sandbox_form.htm" sandbox="allow-scripts"> // TC

    <iframe src="demo_iframe_sandbox_form.htm">

    Injected code does not run in iframe:

    <iframe src="demo_iframe_sandbox_form.htm" sandbox=""> // TC

  • When recording in iframe with the sandbox attribute and the length of source code is less than 256 bytes, TruClient for IE displays a blank page.

Back to top

TruClient Browser

  • TruClient Browser is unable to record and replay actions in dynamic iframe.

    In some AUT pages, some iframes are created dynamically by user actions (for example, by clicking a button). For such iframes, the browser cannot record and replay these actions.

    Resolution: Add the EnableDynamicIframeDetection= setting to the script's default.cfg file (under the "TruClient" section) with one of the following values:

    • 0: Disables the setting.

    • 1: Enables the setting when the AUT document is loaded (on the window.onload event).

    • 2: Enables the setting when the script is loaded to the page.

    Note: Enabling dynamic iframe detection can impact the AUT page’s performance.

Back to top

Internet Explorer limitations using TruClient with VuGen

  • If you are unable to start an IE browser from VuGen or when the script is running in load mode (and running VuGen as administrator does not work), make sure you have the correct registry permissions:

    1. In the Start Menu, either in the Run box or the Search box, type regedit and press Enter.

    2. Locate the following keys, and check you have the following permissions (right-click the key, and select Permissions).

    • Read permissions for HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Internet Explorer.

    • Write permissions for HKEY_CURRENT_USER\SOFTWARE\Micro Focus\TruClient.

    3. Contact your System Administrator to assign the appropriate access level (Read/Full Control) to the key as required.

  • The TruClient—IE protocol does not support Diagnostics for J2EE/.NET.

  • When using a script recorded with TruClient IE and replaying it on Internet Explorer 11, the number of connections measurement is not available in Controller and Analysis.

  • TruClient—IE protocol requires Internet Explorer 11 to be installed on the load generator.
  • TruClient supports only Internet Explorer 11 Standards mode.

  • While the script is running and the application calls cross domain data sources, it may cause the script to hang due to security pop-up launched by the browser.

Back to top

TruClient Browser with VuGen

  • Security warning dialog boxes are not displayed in TruClient during script development.
  • If you encounter problems when running TruClient Browser Vusers in load mode, modify the Pacing settings (VuGen > Replay > Runtime Settings > General > Pacing) as follows: Select either After the previous iteration ends, or At <fixed/random> intervals.
  • TruClient Browser can only be used with applications that support the Mozilla Firefox browser.
  • TruClient Browser does not support Kerberos authentication. If the server also supports NTLM, TruClient automatically moves the authentication to NTLM and continues working.

Back to top

Other protocol limitations

  • When you view Web page component breakdown graphs for TruClient Vusers, TruClient measurements might not be available or might be less accurate than those of other protocols. For example the Time to First Buffer Breakdown graph, and measurements such as SSL Handshake, and Client/Error Time might not be available.
  • TruClient is a UI-based protocol. Therefore, while running a TruClient script in Controller you might encounter an exception: "Failed to Initialize. Reason TimeOut". It is recommend to increase the Init time out. (Controller > Tools > Options)to provide the Vusers with additional time to finalize the initialization stage.

  • TruClient does not support closing dialog boxes opened by user code written in an Evaluate JavaScript step (e.g. window.alert(“my alert”);)
  • After opening TruClient by clicking Develop Script, and subsequently closing it, VuGen may still display the yellow banner of Develop mode.

    Resolution: If working with a proxy, you must specify "bypass local connections". If working with a PAC file, the PAC must specify a direct connection for

  • If you edit a TruClient script using a later version of LoadRunner Professional than the one on which you recorded the script, it may fail to replay in some cases.
    Before modifying the script, save a backup copy of the script.

    Resolution: If the replay fails, rerecord the script using the latest version of the TruClient protocol.

  • TruClient does not record "mouse overs" when the element has a CSS rule of "Mouse Hover".

    Resolution: Instead of mouse hovering, click the elements to open the dropdown (the clicks are recorded).

  • Java applets and Silverlight are not supported for TruClient Browser.

    User actions on UI elements that are based on Java applets and Silverlight technologies are currently not supported for record and replay.

  • In the default Run Block, you cannot set the mode to Random as you can in the VuGen user interface.

  • Some error messages may not be localized.

Back to top