Micro Focus LoadRunner – Tips and Tricks

Table of Contents

2. LoadRunner – Tips and Tricks – Dec 2020

1. Recurrent X in the input box while recording

It often happens that users face recording HTTP/HTML with Vugen while it works properly on the Web browser. Sometimes the VuGen input box appears as an X and it becomes difficult to utilize the recording tool. Even when the Manual Business Process is ongoing and as the input box is present on the screen actively. While VuGen recording’s output remains the same and the input box comes into sight as X. As the application under test (AUT) merely performs in 32bit process on the contrary VuGen can simply initiate at 64bit IE throughout the recording process. A reminder, this fix is only meant for the 1250 version specifically. If the same problem is present in other versions then please make sure to use a ticket with support.

To solve this VuGen running issue, you can use the Fix 1250 with the help of the steps below:

  • Primarily the extraction of the fix.zip file is necessary and then finding these files given below:
  1. QTWeb.Irp
  2. WebBase.Irp
  3. WinSock.Irp
  4. Wplus.Irp
  • After that you need to visit <LoadRunner>\dat\protocols\
  • Then you need to create a copy of all the 4 Irp files mentioned above.
  • Do not forget to close all the Internet Explorer (IE) windows properly. Also force stop and kill all the IEXPLORE.EXE processes before the initiation of the recording process or something could go wrong.

2. The error “Cannot find symbol” occurs in repetition 

Java actions are very important for the functioning of all the Web related activities. When the symbol actions are corrupt or missing then it becomes difficult to operate the Web functions in the Java user protocol. To fix this “cannot find symbol’ error, you can follow the instructions given below:

  • Primarily you need to import a package to the system, and by doing this you will be able to utilize the Java protocols.
  • Now import Irapi.web in the system at the very initial stage of the script carefully. In case it does not get imported, then you will find a message that says “cannot find symbol Actions.java” on the screen.
import lrapi.lr;
import lrapi.web;
public class Actions
{
    public int init() throws Throwable {
        return 0;
    }//end of init
    public int action() throws Throwable {
        web.custom_request("post_query_exe", 
    "Method=POST", 
    new String[]{
        "URL=http://MicroFocus/cgi–bin/post_query_exe",
                "TargetFrame=",
    "LAST"}
);
        return 0;
    }//end of action
    public int end() throws Throwable {
        return 0;
    }//end of end
}

3. Window does not appear with the new step web_convert_param

When Windows does not appear even with the new step web_convert_param then it means that this is a user interface problem. It needs to be fixed quickly, you can solve this issue by following the steps below:

You need to replace the two adjoined configuration files: websteps_steps.dat and WebHTTP.addin

Here, only fix 1260 can be used for the issue particularly. It has been duly effective on the 12.60 version, for a different version or service pack levels a case with support would suffice better. You can find those files in the installation folder in the storage: %vugen_path%

  1. \dat\websteps_steps.dat
  2. AddIns\VuGen\Protocols\WebHttpHtml\WebHTTP.addin

4. When VuGen cannot generate many actions

It often happens that VuGen is not able to generate more than 10 actions in the TruClient protocol. We witness the “maximum amount of actions have been reached” message on the screen. It happens when we are juggling with a lot of actions in the Development mode and once the limit reaches 10 this error shows. To fix this issue you can simply follow the steps provided below:

Specifically for the 1260 version

Just remember that this fix meant for the 1260 version. Once you are done generating 10 actions in the development mode, you need to select any action, record or enter a few codes. 

Then you need to select all the lines and Right click on it.

Then you will see New action, then you need to click on that and create a unique name for it.

Now we need to edit it and make some important changes in the JavaScript file to solve the problem. So Click on Edit File.

Then you will find Irtuclientweb_master_prefs.js under these two destinations:

  1. <install>/day
  2. %AppData%\Roaming\Hewlett-Packard\LoadRunner\TruClientWeb
"TruClient": {
…
      "MaxAllowedActions": {
             "value": 10---------> change to any number
     },

5. VuGen integration problems along with the LoadRunner Enterprise

It often happens that when we paste a server address from the Web, we are only able to copy a Loadtest, admin or LRE, and it doesn’t connect at all. Users are not even able to save the scripts that are initiated or opened from the LoadRunner enterprise while using “https” and “http”. There are not enough files for uploading as run-time files for the DevWeb scripts sometimes at all.  Sometimes it happens that when there is a crowd of various folders in varied paths having the same name the folder tree is unable to grow at all. If the user wants to use a different second script from the same previous project then they would have to re-authenticate again their respective username, password and then select the project. These script related or the integration issues can be solved by following the instructions below:

  1. You need to download the hotfix and then extract LRE_SP2_VuGen_Fix.zip 
  2. You need to find the original “VuGenToolkit.exe” under %vugen_path%\bin\VuGenToolKit and backup it.
  3. You need to find the original “Ire-uploader” folder that is in: %vugen_path%\bin and then backup it.
  4. You need to backup the original “DevWeb.lrp” file that can be found under %vugen_path%\dat\protocols.
  5. Now you have to copy the VuGenToolkit.exe from step 1 to the %vugen_path%\bin\VuGenToolKit\VuGenToolkit.exe.
  6. Then copy the entire lre-uploader folder from Step 1 to the vugen_path%\bin\lre-uploader
  7. Finally copy the DevWeb.lrp 1 to the %vugen_path%\dat\protocols\DevWeb.lrp

6. Error message hinders the completion of the TC script 

While working with the TC script, it often happens that we come across this dialogue box saying “Do you want to leave this site”. Some of the applications on the test will have this same pop up message which later stops the TC script from replaying and proceeding ahead with it. You can put hold to this dialogue box by adding an evaluate javascript. All you have to do is follow the steps given below with the help of the codes:

// Inject this code to all windows
function injectToDoc(doc) {
var scr = document.createElement("script");
scr.type = "text/javascript";
scr.innerHTML = `
window.addEventListener(
"beforeunload",
function(e) {
var rreState = window.top.document.documentElement.getAttribute("hp_attr_state");
if (rreState === "replay") {
console.log("*** setting e.returnValue");
e.returnValue = "TruClient_We_will_let_you_go_";
}
}, true
);
`;
doc.head.appendChild(scr);
}
function doInjection(win) {
injectToDoc(win.document);
const iframes = win.document.querySelectorAll('iframe');
if (iframes.length > 0) {
for (let i = 0; i < iframes.length; ++i) {
console.log(`injecting to iframe: ${iframes[i].id}`);
doInjection(iframes[i].contentWindow);
}
}
}
doInjection(window);

7. Fault in the Internet Explorer injection

Sometimes it happens that there is an internet explorer injection problem. That can be solved single handedly by unchecking the “Enforce standard mode”. You simply have to uncheck it in the TruClient Internet Explorer and investigate if that fixes the problem.  TruClient can also be responsible for injecting code into some web pages so you need to be vary of that. It could also cause irregular or unforeseen behavior of the Application under test (AUT). You can definitely solve this issue so follow the instructions given below carefully:

  1. You need to put a IEInjectionBlacklist.ini file in the script folder. 
  2. To blacklist the particular codes you need to pick out the URLS.

This example is for the “IEInjectionBlacklist.ini” format:

  1. In this fix you will need to use both the URLs and regex:
[Urls]

http://kalimanjaro.hpeswlab.net/webgui/multiplefileform.html

[http://www.google.co.il*]www.google.co.il*

http://16.44.49.218/*/Index.htm

[regexUrls]

^http:\/\/www/\.hpe/\.com\/.*

  1. In this fix you only use urls:
[Urls]

http://kalimanjaro.hpeswlab.net/webgui/multiplefileform.html

  1. In this fix you only use regex :
[regexUrls]

^http:\/\/www/\.hpe/\.com\/.*

If you need to check whether you were successful in blocking the code injection in the browser or the target page then you can try the code below to confirm:

<!doctype html><meta id="hp_injected_meta" http-equiv="X-UA-Compatible" content="IE=edge"> <script type="text/javascript" id="hp_injected_script" src="C:\Program Files (x86)\Micro Focus\LoadRunner\dat\WebIE\RRE\content\injectedCode\injectToAUTWin.js?mode=interactive"></script><!DOCTYPE html>

Then you can simply Right click to view the page and then click on “View Source”. After this if there are no visible signatures like the one mentioned above then you can be steered clear of all your worries. The blacklist fixed the problem completely.

8. Error in generating Transaction summary and response time graphs related

Sometimes there is an error in generating transaction summaries and average transaction response time graphs. In the beginning opening test results in the analysis shows an OK with the data. But later when the whole data is produced it is invalid. The dialogue shows that “Transaction Summary and Average Transaction Response Time graphs were not created”. The users are unable to access the complete data in analysis. It majorly occurs due to the Corrupted Dlls: Analysis.DataLayer.dll and Analysis.loader.dll. This error can be fixed you just need to follow the instructions given below:

  1. You need to download the hotfix.
  2. Make sure to extract all the files.
  3. Then you need to go to the Recycle for the Bin folder to create a backup. This backup is for Analysis.DataLayer.dll and Analysis.loader.dll.
  4. Then you need to replace all of them with the ones that are present in the hotfix folder.
  5. Now all you have to do is restart the analysis tool.

9. Disappearance of transaction counts from the analysis summary page

It happens that at the moment global filters are applied all the transaction counts just vanish. There is not even a speck about the transaction counts in the analysis summary page at all. The reason this error occurs recurrently could be because of the corrupted dil. As crucial as this may seem, this issue can be fixed indeed, just follow all the instructions given below:

  1. You need to download and install the hotfix.
  2. Then you must extract the said files.
  3. Then you need to go to the Recycle for the Bin folder to create a backup Analysis.ChartUI.dll.
  4. Then you need to replace all of them with the ones that are shown in the hotfix folder.
  5. Now all you have to do is restart the analysis tool.

10. Miscalculation error in HTML reports and appearance of wrong values

It seldom happens that users are unable to view the HTML report with accurate values. What actually happens is that it shows incorrect values under the transaction response time that comes under the load graph. Everytime the user tries to open the HTML report it doesn’t show the actual values at all. Even though the report is generated in the analysis tool, the transaction response time under the LG (load graph) does not view any of the user’s information that it is supposed to show. The actual picture from the report should show values from 0 to X but this only shows 0. It has to be a Graphical User-interface testing problem. It could also happen due to the missing or corrupt Analysis.GUI.dll and CSScriptDict.js files.

This problem like any can be solved quite easily if you closely follow the fixes (hotfix) given below:

  1. You need to end all the open and ongoing sessions of the Analysis.
  2. Find the Recycle Bin or Bin folder: <Install Dir>\Micro Focus\LoadRunner\bin
  3. Then find Analysis.GUI.dll file and backup.
  4. Then you need to find the html folder: <Install Dir>\Micro Focus\LoadRunner\bin\html
  5. Then find <Install Dir>\Micro Focus\LoadRunner\bin\html and backup.
  6. Now you need to download the Hotfix.zip file and unzip it.
  7. Now you need to replace Analysis.GUI.dll file first and then Analysis.GUI.dll file next in the bin folder.
  8. You need to repeat this whole procedure in all the devices which have Analysis installed in them. 
  9. Click on Analysis and open it.
  10. Now you have to check the Test results and make a totally new html report.