LoadRunner Recording Playback FAQs and Solutions

1. Recording Error
1) Recording native webtours or recording local website cannot open
This problem occurs when you use Vista's future operating system. This is due to the following content in the local windows\system32\drivers\etc\host file:

     :: 1                        localhost

After you delete it, you can return to normal.

2) When the Web page is recorded, the browser closes automatically when it is opened, or the browser is unresponsive
This is due to the opening of third-party plug-in support in IE, the general installation of QTP will occur this problem.
Just open the IE's Properties menu and find the Advanced option to turn the third-party plug-in support off.
You can also check IE turns off its protected mode, and Windows DEP Data Execution protection is basic for Windows
Programs and services.
3) Browser error when starting recording
This problem is generally due to problems with the installation of the system or incompatible with the version of IE, Vugen 11 is the most compatible with IE 9.0.
4) No script after recording webpage operation
Vugen recording only supports IE and is not well compatible with third-party browsers (LR11 starts to support FireFox
Some versions).
5) Recording the native page can be opened but not recorded to any Events
When the address requested at the time of recording is 127.0.0.1 or Localhost, the problem occasionally occurs, replaced by the system real
IP address.
6) Always prompt for unable to access the server when recording
Consider checking the proxy server settings for IE. Vugen is often seen in Load Runner 8.x
The proxy settings automatically override the behavior of IE 7.0.
7) Recorded Events but stopped recording no script
You can set the port mappings in the recording options to force the system to use some sort of filtering rule for recording on special ports.
8) Use Vugen to start some applications for recording, the application does not start
Not all clients can be vugen loaded, because this client has a certain self-protection function,
Such clients are basically not able to use Vugen direct recording, in this case if you know the client kimono
Protocol format on the server side, you can write your own request to complete the script development.
9) Error when starting Vugen recording
This is generally related to the data protection of the system. Turn on advanced in computer properties, perform protection modifications to data
Enable DEP for basic Windows programs and services only.
2. Replay error
In some cases, the playback script encounters a failure, which generally causes the script to fail for the following reasons
Several:
1) The data in the script has a dynamic part
For example, the script accesses a picture, but the image is deleted on the server when it is played back, which
Script playback, you will naturally get an error indicating that the object cannot be found. The workaround is to modify the code to remove useless
object, or to process Dynamic Data by association.

2) The script is not recorded to all protocol requests
When the system uses a variety of protocols, if we select the recording protocol does not contain all, there will be a missed record request
, and in the event of a lack of partial request impersonation during playback, the subsequent request content is rejected by the server,
The replay failure will occur naturally. The workaround is to verify the system protocol through analysis to ensure that all requests are recorded.
3) The system has problems
In some ways, Vugen is a protocol-based Trojan that may be partially anti-virus software or firewall
Interference and impact, resulting in the inability to access the server normally. The workaround is to turn off unnecessary firewalls and anti-virus when recording
Software.
4) An inappropriate association or checkpoint function was added to the script
When the automatic Recording association rule is turned on in the recording options, the recorded script automatically adds a rule-compliant off
Linked function, and an error is prompted if the associated function cannot capture a target that matches the rule at playback time. Solution built
This feature is then enabled after an in-depth understanding of the association. For the checkpoint function, turn off the Fail function.
5) Server Connection error
The server could not connect, causing the script playback to fail.
In general, playback errors can be located in the log or Test Results, when there is some code debugging
Ability, it can be easily solved.

Excerpt from: Advanced Performance Test Guide--loadrunner 11 Combat (2nd edition)

LoadRunner Recording Playback FAQs and Solutions