LoadRunner Error Message Lister ASP script

The Annoyance

One of the annoyances with LoadRunner is that Report.html files created by LoadRunner Analysis do not have a link to error messages like those displayed by the Controller.

Thankfully, LoadRunner creates an output.mdb file to hold error messages. But, alas, the html report does not refer to it.

Because the output.mdb file is in MS-Access format, some "DBA" skills are necessary to connect the various code tables before the information becomes intelligible.

The database schema changed with v8.1. Reports in v7.8 have different formats than v8.0 and v8.1.

My Solution

So I wrote an ASP script that links the tables together with a SQL query, then displays two views of the output.mdb database: a Summary and Detail view.

I have it running on my IIS server at http://www.wilsonmar.com/asp/lrerrlist.asp

Let me know what you think right away.

Get it and use it ... while it's still free during its beta period ending soon.

How it works

The script uses several Javascript

and ASP

coding tricks. Here's a tour though the program:

When you first invoke lrerrlist.asp, you need to specify a file path such as C:/wherever/output.mdb . This program only works with files named output.mdb.

The ASP program saves the filepath as a cookie on the client, then retrieves it upon every subsequent invocation.

The script shows two diffent views: Sum'ry and Detail. By default, it shows the Summary report upon entry:

Click on the blue number under the #Mes-sages column heading. Notice that the Error Code is automatically filled in.

To display all lines, click on the Error Code field to clear it out.

The Detail view shows a default of 5 rows per page. This behavior can be controlled by changing the number under the R: heading.

The default From and To dates are the maximum values that can be stored. Change it and press "Go" to filter the report more.

The color of report headings and detail lines mimic, by default, the Report.html generated by version 8.0 of the LoadRunner Analysis program. Click on "v7" to change the display to the purple and yellow color of version 7.8.

All the selections are reflected in a field within the Address line at the top of your internet browser. This string can be copied and pasted .

Get It

Since it's an ASP file, this script needs to reside on the IIS server which hosts the Report.html files generated by LoadRunner Analysis program.

So, on the hosting machine:

Invoke a text editor such as Notepad.
click here for the ASP source.
Click on the text, then press Ctrl-A and Ctrl-C to copy the whole file into your Windows clipboard.
Click on the text editor and press Ctrl-V to paste the clipboard's contents in your file.

You must save the file as "lrerrlist.asp" because it refers to itself.

For help in selecting the file path on the same machine, copy and paste my Javascript ActiveX program lrerrpick.htm so that when you're logged on that machine, you can run Microsoft Internet Explorer to click your way to select the Filepath: needed by lrerrlist.asp.

Make It Your Own

To make this work for you:

At your Internet browser's Address bar, type in http://localhost/lrerrlist.asp, but substitute "localhost" with the IP address or name hosting the Report.html files generated by LoadRunner Analysis.
When the screen appears, specify the full path of the output.mdb file.
Click the version of LoadRunner you want to display for.
Click "Go" for the listing.
Invoke the Report.html file generated by LoadRunner.
Right click on the links frame at the left and select "View Source" for the contents.html file.
Copy the line(s) associated with the last item on the list.
Paste the line(s) to create an additional line.
Copy the contents of the LRErrList.asp Address Bar (http://...)
Highlight the URL.
Paste the URL from LRErrList to replace the URL.
Save (replace) the file to where you found it.
Invoke the Report.html again and test the new link.

Put It in Report.html

Each LoadRunner version generates HTML Reports using a different format within file contents.html:

For LoadRunner 8.1, duplicate the block of code such as:

LoadRunner 8.0 (the default), is similar:

For 8.0, add the lines highlighted here (but replace "loadreportserver" with your own server's IP or server name):

http://loadreportserver/LRErrList.asp?D=...

</table>

For LoadRunner 7.8, in file contents.html such as this:

add the line highlighted here:

Output.mdb Internals (Tables and Columns) for V7.8 and v8.x

Within the output.mdb database are 8 related tables. The Main table has column values that are keys to id's in the other 7 tables.

Table Columns

Actions Action_ID, Action_Name (such as vuser_Init)

ErrorHelp ?

ErrorMessages Message_ID, Message_String

ErrorSummary Type, Error_Code, Error_Template, Total_Messages, Area, #Vusers, #Scripts, #Generators

Injectors Injector_ID, Injector_Name (such as IP number)

Main Row_ID, Iteration, Area, Line, Script_ID, Vuser_ID, Injector_ID, Action_ID, Type, Time, Message_ID, Error_Code

MaxSize cMaxSize, cDeletionQuota

Scripts Script_ID, Script_Name

VusersID Vuser_ID, Vuser_ID_Name

strSQL = 
"SELECT Main.Row_ID , Main.Time, Main.Type, Main.Iteration " & _
" , Main.Message_ID ,Main.Error_Code ,ErrorMessages.Message_String " & _
" , Main.Action_ID , Actions.Action_Name " & _
" , Main.Injector_ID, Injectors.Injector_Name " & _
" , Main.Vuser_ID, VusersID.Vuser_ID_name  " & _
" , Main.Script_ID, Scripts.Script_Name " & _
" FROM ((((Main INNER JOIN ErrorMessages ON Main.Message_ID = ErrorMessages.Message_ID) " & _
	" INNER JOIN Actions ON Main.Action_ID = Actions.Action_ID) " & _
	" INNER JOIN Injectors ON Main.Injector_ID = Injectors.Injector_ID) " & _
	" INNER JOIN VusersID ON Main.Vuser_ID = VusersID.Vuser_ID) " & _
	" INNER JOIN Scripts ON Main.Script_ID = Scripts.Script_ID "

Tables for V8.1

Within the output.mdb database for v8.1 are 2 tables for error messages. The ErrorMessage table has an "Error Message" column that is keyed by the "Error ID" column, which is referenced by the "Error_meter" table:

Column Sample Value Description Joint Table

Event Instance ID - - nil

Event ID 0 - Event_map

End Time 1211.906 # days from ... nil

Group ID - - VuserGroup

Error ID - 0... ErrorMessage

Vuser ID - - VuserId

Host ID - - Host

Script ID - - Script

Result ID - - Result

Line Number - - nil

Parent Handle - - nil

Action ID - - ScriptActions

Father ID -1 - nil

Iteration Number 1 - nil

Amaximum 1 - nil

Aminimum 1 - nil

AsumSq 1 - nil

Account 1 - nil

Value 1 - nil

The "Join Table Name" was obtained from the "MetaData" table.

Since the Time is stored as a number of days since an epoch, it must be converted into human-readable text.

The new schema has a "MastersMap" table that contains the SQL query used to create the "T" tables.

strSQL = 
"SELECT Main.Row_ID , Main.Time, Main.Type, Main.Iteration " & _
" , Main.Message_ID ,Main.Error_Code ,ErrorMessages.Message_String " & _
" , Main.Action_ID , Actions.Action_Name " & _
" , Main.Injector_ID, Injectors.Injector_Name " & _
" , Main.Vuser_ID, VusersID.Vuser_ID_name  " & _
" , Main.Script_ID, Scripts.Script_Name " & _
" FROM ((((Main INNER JOIN ErrorMessages ON Main.Message_ID = ErrorMessages.Message_ID) " & _
	" INNER JOIN Actions ON Main.Action_ID = Actions.Action_ID) " & _
	" INNER JOIN Injectors ON Main.Injector_ID = Injectors.Injector_ID) " & _
	" INNER JOIN VusersID ON Main.Vuser_ID = VusersID.Vuser_ID) " & _
	" INNER JOIN Scripts ON Main.Script_ID = Scripts.Script_ID "

Your first name:

Your family name:

Your location (city, country):

Your Email address:

Email me updates

Top of Page

Thank you!