LoadRunner Analysis: “No Stop_Time Value Defined” Error Fix
Posted on Aug, 2014 by Admin
I was running a load test overnight (SOAK) for 10 hours. Something happened overnight, and the Controller machine locked up. I could not log into it or connect to it remotely. It had to be rebooted. When it came back up, I tried to recollate the results for this test and launch LoadRunner Analysis. I received this error message:
I was then prompted to look at the error log. I got: Analysis Error log:
<8/1/2014 9:35:19 AM> Error 75012: in file e:\xxxxx.lrr the Stop_time is 0
I opened up the LRR with the Notepad application. There was no Stop_time variable in the LRR file.
[Scenario] Product=HP LoadRunner Controller Version=12.0.0.0 Path=E:\XXX.lrs Subject=Baseline Result_file=e:\XXXX.lrr Description= ResultName=xxx Time_Zone=21600 Start_time=1406841216 Daylight_Bias=-60 [Configuration] Public_local=1 Is_mix=1 Is_runner_file=0 Runner_file= [Running_mode] Start_reason=By command [Data Collection] FullData=1 [Scenario_summary] Scenario Type=Manual Scenario Goal Profile Name=Schedule 1 Mode=Scenario Scheduling Scenario Duration=Start all Vusers: 2 every 00:00:32 (HH:MM:SS); Run for 08:00:00 (HH:MM:SS); Stop all users: 1 every 00:01:22 (HH:MM:SS) Load Behavior=Initialize all Vusers simultaneously [Scripts] xxx_v4=E:\xxx.usr [Scripts_types] xxxs_v4=Multi+QTWeb
I looked at other LRR files and noted that there was a Start_time variable value missing, in addition to the Stop_reason variable. This Start and Stop time values represent Epoch time – the number of seconds that have elapsed since 00:00:00 Coordinated Universal Time (UTC), Thursday, 1 January 1970. I went to http://www.epochconverter.com/ and punched in the start time value from the LRR file: 
I entered in the start time value and was able to determine the start time of my test for my local time zone. I added 10 hours to the local time and input that into the human date to time stamp. I took that information and added the Stop_time variable and its value (I took off the trailing zeroes – three of them):
Stop_time=1406877216
I added this and Stop_reason=By command into the LRR file so it now looks like this:
[Scenario] Product=HP LoadRunner Controller Version=12.0.0.0 Path=E:\xxx.lrs Subject=Baseline Result_file=e:\xxxx.lrr Description= ResultName=xxx Time_Zone=21600 Start_time=1406841216 Daylight_Bias=-60 Stop_time=1406877216 [Configuration] Public_local=1 Is_mix=1 Is_runner_file=0 Runner_file= [Running_mode] Start_reason=By command Stop_reason=By command [Data Collection] FullData=1 [Scenario_summary] Scenario Type=Manual Scenario Goal Profile Name=Schedule 1 Mode=Scenario Scheduling Scenario Duration=Start all Vusers: 2 every 00:00:32 (HH:MM:SS); Run for 08:00:00 (HH:MM:SS); Stop all Vusers: 1 every 00:01:22 (HH:MM:SS) Load Behavior=Initialize all Vusers simultaneously [Scripts] xxx_v4=E:\xxx.usr [Scripts_types] xxx_v4=Multi+QTWeb
This allowed me to open the Analysis file.
I also recommend Martin Spier’s web site article on this issue. Apparently, this issue is not new.
