How to resolve LoadRunner 500 internal server error while testing an upload file scenario
Scripting a file Upload scenario is usually pretty straightforward, just do few correlations and the script runs without any errors.
But, sometime it becomes complicated when script keeps failing even after correlating all the dynamic values. The most common error encountered while executing the upload script is LoadRunner 500 internal server error .
It may look easier to switch from HTTP/HTML protocol to AJAX truclient in order to resolve the issues but that may lead to different complications, considering –
- AJAX truclient is a GUI based protocol. So, the script during execution consumes more memory on your load generator machine. Therefor the number of users which can be simulated from a load generator is comparatively less
- The script created has to be more dynamic to run without any issues that arise, when application starts performing slow under load.
Below are few tips on resolving the loadrunner 500 internal server error in HTTP/HTML script created for upload functionality.
- Record a new script and compare the requests to identify if any dynamic value has been missed out
- Check, if you have missed to convert the captured values to some special format (PLAIN to URL OR PLAIN to HTML etc.)
- Enable parameter substitution and cross-check the values that are getting substituted are in the same format as the Original recorded format
- The last and most important point is to go to the tree view (toggle to HTML view) of failing request and compare the items in header section for recorded and replay snapshot. You may find some important header missing during replay like a secure token value or something. Add corresponding web_add_header(); before the failing request in the script and re execute.
I hope, by now you would have successfully resolved the issues related to your script :)