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

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 cause of this issue is unknown.

The workaround is as follows:

Press "start" -> "run"

Type "regedit"

Press "Ok"

a) If the Windows installation is 32-bit, navigate to "HKEY_LOCAL_MACHINE/SOFTWARE/Mercury Interactive/LoadRunner/Vugen/Thumbnails"

b) If the Windows installation is 64-bit, navigate to "HKEY_LOCAL_MACHINE/SOFTWARE/Wow6432Node/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.

Advertisements

In PC 11.52, Controller-> Load Generator Agent connection fails with Error: Process “C:\Program Files (x86)\HP\Performance Center Host\\bin\lr_bridge.exe” was not created. Reason: A required privilege is not held by the client. MsgId: MERR-29996

In PC 11.52, Controller-> Load Generator Agent connection fails with Error: Process "C:\Program Files (x86)\HP\Performance Center Host\\bin\lr_bridge.exe" was not created. Reason: A required privilege is not held by the client. [MsgId:
MERR-29996]

This happens ONLY when LoadRunner agent service is run under a service account and works fine when running under default LOCAL_SYSTEM account

This problem happens due to the fact that magentservice will logon with the logon type intended for users who will be interactively using the computer such as a user being logged on through a terminal server, remote shell, or similar process. This will fail in some environments.

Attached fix will change the logon type as a service-type logon that should allow this connection successfully. To install the patch:

1) Download the patch from here on the LG 11.52 machine and unzip it

2) Go to <LoadRunner>\launch_service\bin folder and backup the same set of files as listed in the patch from step 1 and remove them from the folder

3) Copy the files from step1 into the \launch_service\bin folder and restart the LoadRunner Agent Service

4) Attempt the connection again from Controller

This should now work even if agent service is launched with a domain or service account