Vugen Not Recording — Internet Explorer (iexplore.exe) “Hangs” when launched during recording

Vugen Not Recording — Internet Explorer (iexplore.exe) "Hangs" when launched during recording

When recording WEB (HTTP/HTML) script Vugen launches iexplore.exe but Internet Explorer window is not displayed.

This may occur due to COM object permissions.

Change the following Recording Options setting:

"Recording Options" -> General ->"Script": UN-CHECK "Track processes created as COM local servers"

Then record the WEB (HTTP/HTML) script.

Advertisements

“Create correlation” option is disabled for Microsoft .NET scripts

"Create correlation" option is disabled for Microsoft .NET scripts

Sometimes the “Create Correlation” option will be disabled for MS .NET scripts as shown below

This is a known problem for Vugen up to LoadRunner 11 Patch 3 version and is going to be fixed for future versions.

To fix this issue follow the below steps

1) Manually select the value to be correlated by clicking on it.

2) Use the right-click key from your keyboard, located at the right of the space bar.

Error -27778: SSL protocol error when attempting to connect with host

Error -27778: SSL protocol error when attempting to connect with host <hostname>

This will appear on the replay log even after specifying the certificate using the web_set_certificate_ex function:

Error -27778: SSL protocol error when attempting to connect with host "<App’s hostname>" [MsgId: MERR-27778]

The certificate and/or the private key files are encrypted by Windows and Vugen will be unable to send them to the server.

To fix this issue follow the below steps

1) Locate the folder where the certificate and private key files are.

2) Select the certificate file.

3) Right-click on it and select Properties

4) Click on Advanced

5) Un-check "Encrypt contents to secure data".

6) Repeat the steps 2-5 with the private key file.

Error “ifError expired” received with Oracle NCA protocol

Error "ifError expired" received with Oracle NCA protocol

An Oracle NCA protocol script was failing at the end of the script at nca_win_close function with the following error

Error: Error: ifError expired (40)

Applying the required correlations, increasing the Run Time Settings- Oracle NCA-Client Emulation-Pragma Mode- Retry Interval to 60000 milliseconds or using different NCAWaitTimerMode options made no difference in the problem.

This issue can be resolved by modifying the line in appsweb.cfg file located in $OA_HTML/bin directory of the Oracle Forms server from;

record=

to;

record=names

Single virtual user running a multiprotocol script uses more than one license units

Single virtual user running a multiprotocol script uses more than one license units

When running a multiprotocol script in the Controller, each virtual user that runs uses more than one license units. The number of license units used by a virtual user is the same as the number of protocols that are used in the script.

The motivation for this method of license distribution could be better understood if it is taken into consideration that in the early versions of LoadRunner there were no multiprotocol scripts.

In the past the Vuser scripts could only use one protocol – there were no multiprotocol scripts.

Therefore, a license for 100 Vusers corresponded to 100 uses of a single protocol. In the current versions, 1 Vuser running a multiprotocol script of 2 protocols corresponds to 2 Vusers of the old type. Having 50 Vusers running this 2 protocol script corresponds to 100 uses of a protocol and to 100 Vusers of the old type.

That is why a license for 100 Vusers actually means a license for 100 uses of a protocol, not for 100 virtual users.

The Remote Registry service crashes on the Microsoft SQL Server’s machine when adding monitor in LoadRunner

The Remote Registry service crashes on the Microsoft SQL Server’s machine when adding monitor in LoadRunner

When adding a monitor in the LoadRunner Controller, the Remote Registry service crashes on the computer that has SQL Server installed. Additionally, error messages that resemble the following are logged in the Application log on the computer that has the instance of SQL Server installed:

Faulting application name: svchost.exe_RemoteRegistry, version: 6. .7600. 6385, time stamp: 0x4a5bc3c

Faulting module name: perf-MSSQLSERVER-sqlctr 0. .275_unloaded, version: 0.0.0.0, time stamp: 0x4b48 09 Exception code: 0xc0000005

Fault offset: 0x00000000626bfe57

Faulting process id: 0x d 8

Faulting application start time: 0x0 cad723f5bfd536

Faulting application path: Drive:\Windows\system32\svchost.exe

Faulting module path: perf-MSSQLSERVER-sqlctr 0. .275

Report Id: da45823c-4327- df-ad 9-00 7a477845a

Faulting application name: svchost.exe_RemoteRegistry, version: 6.1.7600.16385, time stamp: 0x4a5bc3c1

Faulting module name: sqlctr90.dll_unloaded, version: 0.0.0.0, time stamp: 0x492b1b55

Exception code: 0xc0000005

Fault offset: 0x000000003353c171

Faulting process id: 0x2eec

Faulting application start time: 0x01cad5a366dde911

Faulting application path: Drive:\Windows\system32\svchost.exe

Faulting module path: sqlctr90.dll

Report Id: d0a6f0d5-41b3-11df-ae47-0017a4778006

Additionally, an error message that resembles the following is logged in the Windows System log on the computer that has the instance of SQL Server installed:

Date,Time PM,Error,ServerName,7034,Service Control Manager,N/A,N/A,"The Remote Registry service terminated unexpectedly. It has done this number time(s)."

This issue occurs because the SQL Server Performance Counter uses an incorrect method to call the RegQueryValueEx API to access a registry key. This behavior causes the Remote Registry service that loads the SQL Server Performance Counter to crash.

Microsoft has issued fixes and workaround for this issue. Please refer to Microsoft’s Document ID 2159286 – FIX: The Remote Registry service crashes when an application tries to retrieve performance counter data from an instance of SQL Server on another computer