LoadRunner Tips – 25 Common Issues with Recommendations

LoadRunner is a software testing tool from Micro Focus.  It is used to check applications, measuring system behavior, and performance under load.  LoadRunner can simulate a large number of users recording using program software and assessing the operation of components of the application.

LoadRunner simulates user activity by simulating interactions using the user interface like keypresses or mouse motions or by generating messages between application components.  The interactions that are generated are stored in scripts.  LoadRunner can generate the scripts by recording them, like logging HTTP requests between a client web browser and an application’s server. After you install LoadRunner and start using it you might face some issues.

Below is a list of tips for some common LoadRunner problems. 

Table of Contents

Set the system’s TEMP and TMP directories

Changing the system’s temporary directories

To create a temporary directory:

  • Open Windows Explorer, find a drive that has sufficient space.
  • If the TEMP folder does not exist, create a directory called “TEMP” in the root location of the drive. Example: C:\TEMP

To add/change the temporary environment:

  • For Windows 2000 or Windows XP machine:
    • Right-click on the ‘My Computer’ icon on the desktop and select ‘Properties’.
    • Go to the Advanced tab and click on the ‘Environmental Variables’ button.
    • There are two sections listed: User Variables and System Variables. Under each section, you should see a variable for TEMP and TMP.
    • Double-click on these entries, and modify the location to the temporary environment created above.
    • Click <Apply>.
    • Example: Change from C:\Documents and Settings\<user>\Local Settings\Temp change to C:\TEMP
  • For Windows NT machine:
    • Right-click on the ‘My Computer’ icon on the desktop and select ‘Properties’.
    • Go to the ‘Environmental’ tab.
    • There are two sections listed: User Variables and System Variables. Under each section, you should see a variable for TEMP and TMP.
    • Double-click on these entries, and modify the location to the temporary environment created above.
    • Example: Change from C:\Documents and Settings\<user>\Local Settings\Temp change to C:\TEMP
    • Click <Apply>.

Adding C code to an existing AJAX TruClient script in LoadRunner 11

In LoadRunner 11 external C functions can be called after recording the script with TruClient protocol.

  • Add specific C-code into “C-functions.c” file in VuGen.This file is located in the script directory
  • Insert the “Evaluate C” step from the toolbox 
  • In the step arguments define the function name, which should be called. Currently, only functions without arguments can be used in the “Evaluate C” step. If the functions need arguments create a parameter table and use the parameters to pass the arguments to the function.

Configure the Windows Data Execution Prevention (DEP) feature

Data Execution Prevention (DEP) is a feature that has been introduced with Microsoft Windows XP SP2, Windows Server 2003, Windows Vista and newer versions of the Windows operating systems. This feature performs additional checks on memory to help prevent malicious code from running on Windows platforms. However, DEP may in some cases interfere with the operation of software including LoadRunner components. If unusual behavior is observed when recording scripts, running load tests, or analyzing data then it may be necessary to modify the DEP configuration to continue working.

To modify the Windows XP or Windows Server 2003 DEP configuration

  • Open Start > Control Panel > System.
  • In the Advanced tab, click Performance settings.
  • In the Performance Options Data Execution Prevention tab, select
  • The first option, DEP for essential services only.
  • Click OK to save the settings.
  • Reboot the machine.

To disable DEP completely in Windows XP or Windows Server 2003

  • Click Start, and then click Control Panel.
  • Under Pick a category, click Performance and Maintenance (If the System is not available directly under the control panel).
  • Under or Pick a Control Panel icon, click System.
  • Click the Advanced tab, and in the Startup and Recovery area, click Settings.
  • In the System startup area, click Edit.
  • In Notepad, click Edit and then click Find.
  • In the Find what field, type /noexecute and then click Find Next.
  • In the Find dialog box click Cancel.
  • Replace the policy_level (for example, “OptIn” default) with “AlwaysOff” (without the quotes).
  • WARNING: Be sure to enter the text carefully. Your boot.ini file switch should now read: /noexecute=AlwaysOff
  • In Notepad, click File and then click Save.
  • Click OK to close Startup and Recovery.
  • Click OK to close System Properties and then restart your computer.

If the DEP options are greyed out then it means that DEP is completely disabled.

To enable or disable DEP in Windows Vista, follow these steps:

  • Open an Elevated Command Prompt
    • Open the Start Menu
    • Click All Programs and Accessories
    • Right-click on Command Prompt and click Run as Administrator
    • Click on Continue
  • To Disable DEP
    • In the Elevated Command Prompt, type: bcdedit.exe /set {current} nx AlwaysOff
    • Restart the computer to apply
  • To Enable DEP
    • In the Elevated Command Prompt, type: bcdedit.exe /set {current} nx OptIn
  • Restart the computer to apply

DEP Options:

  • AlwaysOff: DEP is disabled for all processes.
  • AlwaysOn: DEP is enabled for all processes.
  • OptIn: DEP is enabled for only Windows system components and services that have DEP applied. This is the default setting.

Windows limitation of maximum path length on the temporary directory of Performance Center Load Generator

If while running VuGen scripts in Performance Center the following error appears:

“Error: The user files were not transferred to the local load generator”

The controller cannot transfer the script files to the Load Generator.

When running a scenario in LoadRunner Controller / Performance Center, the Controller transfers the Vugen script files to the temporary location on the Load Generators. The temporary location will be created under <the load generator’s temporary directory>\<brr folder>\netdir\<Path to the results folder on the controller>\<results name>.

READ  Filter out URL in AJAX TruClient Script

For example, if the script in Controller is stored in c:\VugenScript\Script1 and the Load Generator has the temporary folder set to C:\Documents and Settings\Default User\Local Settings\Temp, the Load Generator would save this script file in C:\Documents and Settings\Default User\Local Settings\Temp\<brr folder>\netdir\c\VugenScript\Script1.

This is caused by a limitation of the maximum path length on Windows OS. The length limitation is 255 bytes in Windows XP and 260 bytes in Windows Vista. Please refer to MSDN: File Names, Paths, and Namespaces(http://msdn.microsoft.com/en-us/library/aa365247(VS.85).aspx) for more details on this limitation.

To fix this issue, on the Load Generator:

  • If you are running the agent as a process, you can change the “TEMP” system Variable of the user from C:\Documents and Settings\Default User\Local Settings\Temp to C:\Temp.
  • If you are running the agent as a service, you can change the service to use an account with Administrator privileges, and change the admin account’s “TEMP” system variable to a shorter path:
    • Go to Start -> Control Panel -> Administrative Tools -> Services.
    • Look for the LoadRunner / Performance Center Agent Service.
    • Right-click and select Properties->Log On, changing this from “Local System account” to “This account”, supplying the Administrative account username and password.
    • Change the admin user’s temporary location.

VuGen script recording is slow and the recording platform occasionally becomes CPU bound

When recording a Citrix script, if the recording activity is very slow and the recording platform sometimes becomes CPU bound and peaks of 100% of CPU being used is observed. However, if VuGen is restarted or the recording platform is rebooted, recording performance is initially normal.

The reason for this could be that the Data Execution Prevention (DEP) feature is enabled on the recording platform. Disabling the Data Execution Prevention (DEP) feature using the procedure described in How to configure the Windows Data Execution Prevention (DEP) feature should resolve this issue.

Change the 90th percentile column in the summary report to other values

Modifying the .asc file to reflect the desired percentage will change the percentile in the summary report.

Note: Please disable the default template when you implement the changes:

  • Open Analysis, and go to Tools -> Templates -> Apply/edit templates
  • Uncheck every option.
  • Make the changes for percentile 

After changing the percentile, bring up your graph and recreate the template.

  • Open Analysis
  • Go to Tools -> Options …
  • On the ‘General’ tab, change the ‘Transaction Percentile’.

Since this is an application-level setting, the column name changes to the new percentile figure only on the next invocation of Analysis. In order for the changes to be reflected on current session Go To Tools-> Options -> Result Collection and Click on “Apply Now on Active Session”

90th Percentile – Definition, Calculation

To understand the performance of an application it is important to understand the concept of percentiles. A percentile is a measure used in statistics indicating the value below which a given percentage of observations in a group of observations fall. For example, the response time for a HTTP request below which 90% of the response time values lie, is called the 90-percentile response time. In the screenshot below this is 3.0 seconds (so 90 percent of the requests is processed in 3.0 seconds or less:

LoadRunner 90th percentile

The 90th percentile is the value for which 90% of the data points are smaller

The 90th percentile is a measure of statistical distribution, not unlike the median. The median is the middle value. The median is the value for which 50% of the values were bigger, and 50% smaller. The 90th percentile tells you the value for which 90% of the data points are smaller and 10% are bigger.

Statistically, to calculate the 90th percentile value:

  • Sort the transaction instances by their value.
  • Remove the top 10% instances.
  • The highest value left is the 90th percentile.

Example:

There are ten instances of transaction “t1” with the values 1,3,2,4,5,20,7,8,9,6 (in sec).

  • Sort by value — 1,2,3,4,5,6,7,8,9,20.
  • Remove top 10 % — remove the value “20.”
  • The highest value left is the 90th percentile — 9 is the 90th percentile value.

Error: “URL Security cannot be asserted.” returned from login step in correlated Oracle Applications R12 script

If you have correlated a Web Protocol script recorded against an Oracle Applications R12 application, the login step continues to fail and the following message:

URL Security cannot be asserted. The given URL has either expired or has been tampered with. Please contact your System Administrator for help.

is displayed in the page returned by the server.

The default correlation performed by VuGen may not select the correct value for the “oas” parameter and consequently the login step fails during replay. This message indicates that a correlated value in the URL sent to the server during script replay is not correct. This is due to an incorrect correlation.

Typically the login step is performed by a “POST” action such as:

web_submit_data("OA.jsp",
"Action=http://frsdev.moe.gov.sa:8000/OA_HTML/OA.jsp?page=/oracle/apps/fnd/sso/login/webui/MainLoginPG&_ri=0&_ti={WCSParam1}&language_code=US&requestUrl=&oapc=2&oas={WCSParam2}..",
"Method=POST",
.
.
LAST);

If an incorrect correlation of the value of the “oas” parameter is performed, this login step will fail.

To fix this issue typically there may be several different values for the “oas” parameter present in data returned by the server to the client during the recording of the business process. The value that is required for this parameter for the login step is returned by the server within the following content:

Action.c(nnn): method="POST" action="/OA_HTML/OA.jsp?page=/oracle/apps/fnd/sso/login/webui/MainLoginPG&_ri

Action.c(nnn): =0&_ti=1963387896&language_code=US&requestUrl=&oapc=2&oas=_puaepcRLdyxa9Nwu4WQqw.."><input

and therefore the correlation statement that is required should be similar to:

web_reg_save_param("WCSParam2",
"LB/IC=language_code=US&requestUrl=&oapc=2&oas=",
"RB/IC=..\"",
"Ord=1",
"Search=body",
"RelFrameId=1",
LAST);

Error running more than two Citrix Vusers in load test only: “Error: Got unexpected disconnect event, exiting …”

When running a load test using the Citrix protocol, more than two Vusers fail with the error “Error: Got unexpected disconnect event, exiting …”

Starting with the Citrix XenApp plugin v 11.2 and onward, the LoadRunner Agent must run as a process. By default, it runs as a service.

Change the LoadRunner Agent on the load generator to run as a process rather than a service. One way this can be done by using the HP LoadRunner Agent Run Time Settings configuration tool (in Start|All Programs folder), and selecting “manually log in to this machine”.

NOTE: It is not recommended to run Citrix Vuser scripts on the LoadRunner controller, other than for troubleshooting purposes, rather separate load generators should be used.

Error -86801: Host access denied, not available or missing

Media Player scripts fail with the error: Error -86801:Host access denied, <hostname> not available or missing.

To fix this issue, Call the mms_disable_host_check function in all Media Player scripts

Capture a dump of a crash using the “ntsd” tool

If a LoadRunner component (VuGen, Controller, Analysis, mdrv, etc) crashes during use, further information is required to allow LoadRunner R&D to investigate the issue. One of the most useful means to analyze the root cause of the crash is the call stack from the crash, which when combined with the source code allows the identification of the problem and provision of a workaround.

To generate a crash dump file:

  • Verify that “ntsd.exe” is present in the “windows\system32” folder. In some versions of Microsoft Windows this executable is missing and can be downloaded from the Microsoft website,
  • Start the business process,
  • Open Windows’ Task Manager (WTM) and get the ID of the process that is crashing (in WTM, use View->Select Columns… and tick the “PID (Process Identifier)” item),
  • Open command line (start -> run -> cmd),
  • Type “ntsd -p <ID retrieved in step (3)>. This operation will attach the debugger to the process and while it happens the process will be paused,
  • Type “g” after the step (5) finishes to continue with the process’s run,
  • Once the crash occurs, type “.dump <full file path>”. For example “.dump c:\temp\mydump.dmp”.
  • Provide the details of the scenario in which the crash occurs along with the dump file.
READ  How to record and replay against a JAR executable

Add a custom monitor to LoadRunner Analysis

To add a custom monitor to LoadRunner Analysis

  • Discover the offline reported event type.
    • In the offline def files in the result directory (e.g., “offl_0.def”), search for a file reporting one of the monitor’s measurements.
    • Verify it is the correct monitor file and not some other monitor (check the “GraphGroupMenuTitle” key).
    • Search for a key called “GraphType,” or a key called “GraphGroupMenuTitle” if the GraphType key does not exist. Call this key value even type.
  • Create a definition file for this graph.
    • Copy one of the existing database definition files (Oracle.def or SQLserver.def) and rename it (e.g., “MyDBmon.def”). In this case, “MyDBmon” is the template name.
    • Note: The user will not see this name in any way.
    • Update this file.
  • Update the graph’s title (a key called “Title” in the “BasicInfo” section – the user will see this).
  • Update the description (a key called “Description” in the “BasicInfo” section – the user will see this).
  • Update the event type (a key called “EventType” in the “BasicInfo” section – should be the same as the event type from the offline def files).
  • Update the basic filter value (a key called “Values” in the “BasicFilter0” section – should be the same as the event type from the offline def files).
  • Note: The help context for the new graph will not be updated.
  • Add the new graph to the UI. Go to the <LoadRunner>\bin\dat\GeneralSettings.txt file, in the section called “Database Server Resources,” add the new graph and update the number of graphs. The new section should look like this:
[Database Server Resources]
NumGraphs=3
Graph0=Oracle
Graph1=SQLserver
Graph2=MyDBmon

Note: The name you entered here (in this case, “MyDBmon”) should be the template name (the definition file without the “.def” extension). The user will not see this name in any way.

Set the Summary Report to display transactions in the order of execution

Modify the SQL query in the AnalysisSummary.asc file to set the Summary Report to display transactions in the order of execution

  • Close Analysis.
  • Go to <LoadRunner/Performance Center>\bin\dat and open AnalysisSummary.asc in a word editor.
  • Locate the [Line12_Field0] section.
  • Locate the line for JoinedSelectString.
  • Replace the SQL query with the following:
SELECT [Event_map].[Event Name] AS [Event Name],[Minimum],[Average],[Maximum],StdVal,[Table2].[Value] AS [90 Percent], Round([PassedT].[CountAll],0) AS Pass, Round([FailedT].[CountAll],0) AS Fail, Round([StoppedT].[CountAll],0) AS Stop FROM (((((Event_map LEFT JOIN [Table1] ON [Table1].[Event Name] = [Event_map].[Event Name]) LEFT JOIN (SELECT * FROM [Table0] WHERE [Transaction End Status] = ‘Pass’) AS PassedT ON [Event_map].[Event Name] = [PassedT].[Event Name]) LEFT JOIN (SELECT * FROM [Table0] WHERE [Transaction End Status] = ‘Fail’) AS FailedT ON [Event_map].[Event Name] = [FailedT].[Event Name]) LEFT JOIN (SELECT * FROM [Table0] WHERE [Transaction End Status] = ‘Stop’) AS StoppedT ON [Event_map].[EventName] = [StoppedT].[Event Name]) LEFT JOIN [Table2] ON [Event_map].[Event Name] = [Table2].[Event Name]) LEFT JOIN [TempForSummaryRep0] ON [Event_map].[Event Name] = [TempForSummaryRep0].[Event Name] WHERE [Event_map].[Event Type] = ‘Transaction’ and ([Table2].[Percent] = 90 OR [Table2].[Percent] Is Null) GROUP BY [Event_map].[Event Name],[Event_map].[Event ID], [Minimum],[Average],[Maximum],StdVal, Round([PassedT].[CountAll],0), Round([FailedT].[CountAll],0), Round([StoppedT].[CountAll],0),[Table2].[Value] ORDER BY [Event_map].[EventID]
  • Open Analysis and open the results.

VuGen in LoadRunner crashes when opening the parameter list

The following error message is displayed in the VuGen user interface when either accessing the parameter list or attempting to parameterize a value in a script:

VuGen caused an EXCEPTION_ACCESS_VIOLATION in module MFC80.DLL.

The cause of this is because a product that updates the mfc80.dll module (for example, SQL Server 2008) is installed in the affected machine. After this module is updated applications such as VuGen which are developed in Visual Studio 2005 will hit an access violation in the mfc80.dll module and then crash. The problem is due to version incompatibility.

This problem is documented by Microsoft. The fix and further information about the problem are available at the following link: http://support.microsoft.com/kb/961894

VuGen hangs when trying to create parameters

When trying to create a new parameter in VuGen, the CPU utilization for VuGen.exe goes up to 100% and stays there eventually causing VuGen to crash.

The reason for this is because the ss32x25.ocx file was not registered on the machine.

To fix this issue register the ss32x25.ocx file on the VuGen machine.

  • Check if ss32x25.ocx exists in C:\WINNT\system32 or C:\windows\system32 where it is copied to during the LR/VuGen installation.
  • Check the version of the .ocx file, and confirm it is 2.5.0.20.
  • Note: If the file is not present or the version is a lower one, copy it from a working LoadRunner machine, or, it can be found in the LoadRunner installation DVD, under this folder: lrunner\MSI\setup_j\register
  • Register the ss32x25.ocx file using regsvr32.

Use the regsvr32 command to register or unregister a DLL

To register a DLL or OCX file

Method 1:

  • Open a DOS window.
  • Navigate to the DLL’s or OCX’s directory.
  • Enter regsvr32.exe <filename>.<dll/ocx>
    • Example: regsvr32.exe mylibrary.dll

Method 2:

  • Go to Start -> Run and enter regsvr32.
  • Open Windows Explorer and find the file.
  • Drag the file from the Windows Explorer window into the Run dialog window. This will enter the full path to the DLL or OCX file.
  • Click <OK>
    • Example: regsvr32.exe “c:program filesMercurymylibrary.dll”

To unregister a DLL or OCX file

Method 1:

  • Open a DOS window.
  • Navigate to the DLL’s or the OCX’s directory.
  • Enter regsvr32.exe /u <filename>.<dll/ocx>
  • Example: regsvr32.exe /u mylibrary.dll

Method 2:

  • Go to Start -> Run and enter regsvr32 /u.
  • Open Windows Explorer and find the file.
  • Drag the file from the Windows Explorer window into the Run dialog window. This will enter the full path to the DLL or OCX file.
  • Click <OK>

VuGen keeps crashing and/or menu items are not working

If the VuGen crashes when stopping a recording session thereby causing problems in saving the script, it does not show all the toolbar icons or floating recording toolbar is missing, this happens when some DLLs are not registered properly or some configuration files are corrupted.

Below are the steps to re-register the DLLs and to re-create the configuration files:

  • Make sure all the LoadRunner applications are closed.
  • Go to <LoadRunner>\ directory and execute (double-click) run_before_finish.bat
  • Go to C:\Winnt, back up VuGen.ini, then delete the file. LoadRunner will recreate new configuration files when VuGen is launched.

Note : It is always a good practice to keep the background processes to the minimum when recording as they may conflict with VuGen hooking, and may cause crashes during or after recording. Shut down all unnecessary programs before recording a script.

Web recorder hangs when switching Actions on the toolbar during recording

This occurs when the recorder needs the context from a previous Action in order to determine what to record. By default, “Reset Context for each action” in the Recording options is enabled. This option resets the HTML context, so that a contextless function is always recorded in the beginning of the Action. It also clears the cache and resets the usernames and passwords (enabled by default).

READ  Error -205177: Failed to startup RRE due to a timeoutfunction xlrCReplayEngineStartupNotifier::WaitForStartupNotification

To fix this issue, Clear the “Reset Context for each action” option in the Recording options -> Internet Protocol:Advanced section.

VuGen hangs when trying to open a large “replay.vdf” file

After recording a Tuxedo script, one of the files attached to the script is “replay.vdf.” When trying to open it, or scrolling down on it, the VuGen Editor hangs. This happens because the replay.vdf file is large, colorful and uses a lot of comments.

In order to improve performance implement the below steps:

  • Cancel the coloring of C-Comment and improve the opening of the file.
    • Go to C:\winnt and bring up VuGen.ini.
    • Under the section for [General], add: MaxCommentLine=0 ;
  • Hide reply buffers from the server from the replay.vdf file. (Note: This can make it hard to correlate the script, but will significantly cut down the size of the replay.vdf file.)
    • Go to C:\winnt and bring up VuGen.ini.
    • Under the section for [TUXEDO], add/modify: SHOW_REPLIES=0

Internet Explorer freezes randomly when recording a Secure Web application

In secure http communication, the “handshake” syncs the server and the client up with the encryption methods and keys that will be used for the remainder of the communications. A successful handshake creates the new “secure key” that the remainder of the connection will be using. In this case, the Client tries to set up a secure connection (ssl handshake) every time, instead of using the “secure key” that was created during the first successful handshake, for the remainder of the session. The ssl handshake succeeded on some attempts but was failing on other requests, and that is why Internet Explorer froze randomly at different steps in the Business Process with the below error messages

[Net An. Warning (1590: d10)] Request Connection: Remote Server @ xx.xxx.x.xxx:443 (Service=) Failed attempt #1. Unable to connect to proxy (@ xx.xxx.x.xxx:xxxx): sid = xxxx, rc = 10056)

[Net An. Warning (1590: d10)] Request Connection: Remote Server @ xx.xxx.x.xxx:443 (Service=) Failed attempt #2. Unable to connect to proxy (@ xx.xxx.x.xxx:xxxx): sid = xxxx, rc = 10056)

To fix this issue, In the Registry change

[HKEY_CURRENT_USER/Software/Mercury Interactive/LoadRunner/Protocols/WPlus/SSL/OpenSSL] “ReuseSSLSession” value to 1

By doing this, you are ensuring that the “secure key” created during the first successful ssl handshake, is reused for the entire session instead of the client trying to do a ssl handshake every time.

VuGen crashes/hangs while recording a client-server application using ODBC

VuGen may also crash with various errors such as the followings:

  • “int_line() – MEM_ALLOC returns NULL”
  • “vugen.exe – Application error”
  • “The exception unknown software exception (0xc0000fd) occurred in the application at location 0x77f8e52f.”
  • “The instruction at “0x5f401351” referenced memory at “0x00000004”. The memory could not be “read”.”

The reason for these errors is that the application is returning a large chunk of data to the client, and the recorder is trying to put that data in the recording log.

To fix this issue, make the Trace and ASCII file detail levels “Brief Trace” or “Off” in the recording options

Before you start to record,

  • Go to Tools -> Recording options -> Advanced.
  • Change the Trace detail level to “Brief Trace” or “Off.”
  • Repeat the same for the ASCII file detail level.

VuGen crashes with Web and FLEX protocols

When creating a Multi-Protocol Script that contains FLEX and WEB protocols (or Multi Web protocol) a VuGen crash can occur without any error messages. This happens when the WEB protocol is set to be in HTML Mode. When in URL mode the crash does not occur. There are no error codes except a generic Windows message stating the application crashed.

This issue can be seen on machines that are running Windows XP. Please refer to the Microsoft KB article in the link below that can correct this VuGen Crash. Microsoft released a hotfix for a Windows-specific issue that can cause this VuGen crash.

Error -205177: Failed to startup RRE due to a timeoutfunction xlrCReplayEngineStartupNotifier::WaitForStartupNotification

Error -205177: Failed to startup RRE due to a timeoutfunction xlrCReplayEngineStartupNotifier::WaitForStartupNotification

During the replay of an Ajax TruClient script in Vugen or the Controller the following error was observed:

Error -205177: Failed to startup RRE due to a timeoutfunction xlrCReplayEngineStartupNotifier::WaitForStartupNotification in .\xlrReplayEngineStartupNotifier.cpp(82), modified Sun Sep 5 16:57:31 2010, compiled Sep 14 2010 08:22:14 [MsgId: MERR-205177]

Error -205177: Internal Error – Failed on Wait for Startup [MsgId: MERR-205177]

The reason for this is because the script was saved in a UNC path location (network drive) and is missing files from the RRE folder where the script is saved.

To resolve this issue try one of the below options:

  • Option A: First save the script locally and then save it in the UNC path.
  • Option B: Save the script in the UNC path
  • Open the script directory
  • Rename the RRE folder
  • Reopen the script

Unable to generate an analysis report for large result sets

Getting Parsing error with large result sets (less than 2 GB).:

Parse Command line error:

Unable to cast COM object of type ‘System._ComObject’ to interface type ‘Borland.Vcl.Fields’. This operation failed because the QueryInterface call on the COM component with IID ‘{XXXXXXXXXXXX}’ failed due to the following error:

No such interface supported. (Exception from HRESULT XXXXXXXXX (E_NOINTERFACE)).

Note: Small result sets work just fine on the same machine.

The cause is due to taking a lot of resources. The workaround is to change the Data collection option from “Generate Summary data while generating complete data’ (third option which is the default) to “Generate Complete data” which is the second option in the Analysis which is available under Analysis —-> Tools

Verify the arguments provided in web_set_certificate_ex() are correct

  • On the vugen machine, open a DOS window and navigate to LoadRunner Installation bin folder (i.e. <LoadRunner>\bin).
    • Type in: openssl and hit <enter>
  • Type in: s_client -connect <host:port> -cert <certificate name along with path in PEM format> -key <the path to the private key to use in PEM format> -passwd <the private key password>

If the above command works, then the arguments provided in web_set_certificate_ex() are valid.

Example: s_client -connect ivorde.ro:443 -cert example.pem -key keyex.pem -pass 1234

VuGen gives exception error at the end of the recording or during replay due to thumbnails

If you are getting the following pop-up error at the end of the recording:

AXWIN Frame Window: thumbprocess.exe – Application error

The instruction at ” 0x7dc995fe” referenced memory at “0x02b87cf4”. The memory could not be “read”.

Click on OK to terminate the program. Click on CANCEL to debug the program.

The workaround is as follows:

  • Press “start” -> “run”
  • Type “regedit”
  • Press “Ok”
  • Navigate to “HKEY_LOCAL_MACHINE/SOFTWARE/Mercury Interactive/LoadRunner/Vugen/Thumbnails”
  • Double-click on “GenerateThumbs,” and set the value to 0.

Now try doing a recording (or replay if the issue was during replay) with VuGen

Recommended Articles