What is the STEP DOWNLOAD TIMEOUT ERROR IN LOAD RUNNER

ERROR: “-27751: STEP DOWNLOAD TIMEOUT (120 SECONDS) HAS EXPIRED WHEN DOWNLOADING RESOURCE(S)…” EVEN THOUGH TIMEOUT IS SETThe following error occurs even after setting receive and connect timeouts in the script using the web_set_timeout() function:

Error -27727: Step download timeout (120 seconds) has expired when downloading resource(s). Set the "Resource Page Timeout is a Warning"
This error indicates that the page download timeout limit has been exceeded. To specify a different limit value, do the following:
Go to Run-Time settings,

Go to Internet Protocol -> Preferences and select the "Options" button,

Change the "Step DownLoad Timeout (secs)" from the default value of 120 seconds to the desired value.

Note that in the Run-Time Setting dialog, the maximum limit for step download timeout is 32000 seconds. To specify an increased limit, use the web_set_timeout() function as follows:
web_set_timeout(STEP, "xx"); //for regular web Vuser
web.set_timeout(STEP, "xx"); //for regular Java / JavaScript Vuser

The Step Download Timeout encompasses all requests made from a single LoadRunner statement. For example, a step in the script may consist of a single request to the server, or may consist of 10 requests. For example an HTML mode web_url request to http://www.google.com would consist of an initial request to the Google server for the main HTML file. After parsing this HTML file, further additional resources will be downloaded (e.g. .gif files). In HTML mode, these resources are downloaded automatically as a part of the web_url for http://www.google.com. Thus, the Page Download Timeout will encompass all the requests, that is, the initial request and the requests arising from any related resources).

Step Download Timeout means that the step needed to performed for the subsequent step to be performed have reached its timeout limit (default is 120 secs) in LoadRunner. A more detailed explanation can be found in KB 15370 .

Having mentioned the above, there are situations we must take note when this error occur. If the error occurs during the generation of the script (replay in Vugen), it could mean that the application is really taking time of more than 120 secs to complete the download of the resources. You may want to configure the timing to suit your application needs.

If the error occurs during a scenario execution and happens in the middle of the scenario (usually with a large amount of load), the application is handling alot of load and unable to attend to all the vuser request, thus (maybe) taking more than the configured download timing. For this, it will be better advisable to look at the system utilization of the servers to seeth out any performance problems.

To determine the initial problem, we can ask the following questions.
1. Does the error occur in Vugen?
2. Does the error occur in Controller?
3. If yes for (2), does it occur in the start of the scenario run or in the middle of the
scenario run?
4. If yes for (2), what is the amount of running users when the error occur?
The above, can scope down to the area of problem and allow you to determine your next course of action.
If you have decided that the Step Download Time needs to be configured, you can configure that in the Runtime Settings of the script

LoadRunner Training in Bangalore

LoadRunner Training in Hyderabad

LoadRunner Online Training

LoadRunner Training in BTM

LoadRunner Training in Marathahalli

Best LoadRunner Training Institutes in Bangalore 

Best LoadRunner Training Institutes in India

Training Institutes in Bangalore