LoadRunner script playback problem and its solving method

In the running of the script playback, there are sometimes errors, which is unavoidable in the actual test, after all, the automatic recording generated by the script will inevitably have problems, need to run a script to verify that the problem is resolved before adding to the scene for load testing. The following is a solution to the problem that occurs when you replay a script that is recorded with a common protocol, such as a Web, Web services protocol.

It is important to note that the errors that occur while replaying a script are sometimes caused by the program itself, so you must ensure that the script is recorded correctly before you troubleshoot the script playback problem.

1.LoadRunner Timeout Error: Timeout occurs frequently when recording Web protocol script playback, and there are many reasons for the error, and the solution is different.

Error 1:ACTION.C: Error-27728:step download timeout (seconds) has when expired (s).

Error analysis: For the HTTP protocol, the default timeout is 120 seconds (which can be modified in LoadRunner), the client sends a request to the server side, and if the server side has not returned a result for more than 120 seconds, a timeout error occurs.

WORKAROUND: Set the timeout in the running environment first, the default timeout can be set longer, set multiple iterations to run, and if there is a time-out, it needs to be in "Runtime Setting" > "Internet protocol:preferences" > Set a "winlnet replay instead of sockets" option in the "Advanced" area to replay the success.

Error phenomenon 2:ACTION.C (Bayi): Continuing after error-27498:timed out while processing url=http://172.18.20.70:7001/workflow/ Bjtel/leasedline/querystat/suborderquery.do

Error Analysis: This error is often because the concurrent pressure is too large, the server is too busy, can not respond to the client's request in a timely manner, so this error is normal phenomenon, is caused by too much pressure.

If the problem occurs when the pressure is very small, it may be that there is a mistake somewhere in the script and you have to look carefully at the script, and the error message that prompts you to locate a specific problem.

Workaround: For example, the error phenomenon above is positioned on a URL, and you need to run the scene again and access the URL on another machine. If it is inaccessible or too long, it may be a server or this application cannot support such a large load. Analysis of the server, it is best to optimize its performance.

If there is a timeout after running the scene again, you should analyze the reasons in various graphs, for example, you can see if there is a problem with the server, DNS, network, etc.

Finally, add the Run-time timeout setting, in "Run-time settings" > "Internet protocol:preferences", click "Options", and add "Http-request Connect Timeout "or" Http-request receive "value.

2.LoadRunner script garbled: In the recording of the Web protocol script in Chinese garbled, in the playback script will make playback stop in garbled location, script can not run.

Error phenomenon: A link or picture name is garbled in Chinese, script can not run through.

Error Analysis: Script recordings may be in the url-based script, and if the program defines a character set that uses international standards, the script will appear garbled.

Workaround: Re-record the script, open the Recording Options Configuration dialog box before recording the script, select "Surport Charset" in the "Advanced" option of "recording options", and then select the option to support "UTF-8".

3.LoadRunner HTTP Server Status code: In the process of recording a Web protocol script playback script,

The HTTP Server status code appears, such as a common page-404 error tip,-500 error message.

Error 1:-404 the not found server does not find a resource that matches the request URI, but it can continue to run until the end.

Error Analysis: The resources that match the request URI are already submitted once when the script is recorded, and the same resources cannot be repeated at playback time, but the content of the submitted resource needs to be changed, each time the script is replayed to change the submitted data to ensure the simulation of the actual environment, causing a certain load pressure.

Workaround: Make a script association where the error occurs, and insert the corresponding function if necessary.

Error phenomenon 2:-500 Internal Server error Server internal errors, script run stop.

Error Analysis: The server encountered an unexpected condition that prevented it from continuing to respond to requests.

Solution: This error is fatal, indicating that the problem is very serious, need to check from the location of the problem, the developers need this program to solve, and the reason for the cause according to the actual situation, testers can not solve the problem alone, and should be resolved as soon as possible in order to test later.

4.LoadRunner request cannot be found: in the process of recording a Web protocol script playback script,

A request cannot be found, causing the script to stop running.

Error phenomenon: action.c: error-27979:requested form. Not found [msgid:merr-27979]

ACTION.C (a): Web_submit_form. Highest severity level is "ERROR", 0 body bytes, 0 header bytes [msgid:mmsg-27178] "

The associated URL for this component is not visible in tree view at this time.

Error Analysis: The selected recording script mode is incorrect, and typically, browser-based Web applications use "html-based script" mode to record scripts, without browser-based Web applications, Web applications containing Java applets that interact with the server, browser-based applications include Javascript/vbscript code that communicates to the server, HTTPS security protocols are used in browser-based applications, and recordings are performed using "url-based script" mode.

Workaround: Open the Recording Options Configuration dialog box and select "Recording level" to "recording" in the "Protocol" option of "recording options" for "html-based" Script, click HTML Advanced, and select Script. Type as script. Containing explicit ". Then choose to record the script using the url-based script mode.

5.LoadRunner do not perform check method: Added a check method Web_find in the Recording Web protocol script, but did not perform during script playback.

Error phenomenon: Insert function web_find in script, set text and checkpoint of image in script, but do not check the set checkpoint during playback, that is, web_find invalid.

Error Analysis: Because the check function consumes a certain amount of resources, so loadrunner the text and the image by default, so after setting the checkpoint, you need to turn on the check function.

Workaround: Open the Run Environment Settings dialog box to set the "Enable Image and text" under "Check" in "Perference" in the "Internet Protocol" option of "Run-time settings" Check option.

6.LoadRunner Playback Web Services Protocol script error: LoadRunner version 8.0 is normal when you record a script for a Web services protocol, but an error occurs while playback prompts you to stop the script from running.

Error: The script that uses LoadRunner version 8.0 to record Web services protocols does not have any error prompts, and the following error appears when replaying the script "Error:server returned an incorrectly formatted SOAP response ".

Error Analysis: This error occurs because LoadRunner8.0 has a flaw in recording the script for the Web Services Protocol:

If the server's operating system is in Chinese, Vugen will automatically change the header of the WSDL file so that this error is not prompted.

Workaround: Download two patches, respectively "Lr80webservicesfpi_setup.exe" and "Lrunner_web_ Services_patch_1.exe" installed.