Mastering a tool like LoadRunner requires familiarity not only with its features and functions, but also its quirks and workarounds. For example, LoadRunner occasionally runs into a problem while a test scenario is running and any attempt to open the results file throws an error. We have identified recovery procedures that can save many hours of retesting. Here are four methods, from simple to complex, that you can try. Be sure to back up your .lrr folder before attempting any of them.
The first method is to force re-collation of the results. This can be done by changing “Completed” from 0 to 1 (as needed) in Collate.txt, then invoking the Collate Results controller action.
The second method is to copy the .eve and .map files and log folders from each load generator to the controller .lrr folder, then running Collate Results.
The third method is to manually repair the .lrr file to add missing section separator lines, fix the FullData flag, and add a stop time or scenario duration as needed.
The fourth method is to run the same test for a short duration to record control information, then replacing the results with those from the original run. This requires saving the results in a separate folder, patching the start time to match the original full-length run, replacing the .eve and .map files and log folder with the original results from the load generators, and copying the data from the original .lrr folder to the new one. It should now be possible to analyze the results.
We love sharing our expertise in LoadRunner. If you are interested in detailed procedures, please feel free to contact us using our Contact Form.