Reporting Services LogViewer Tool


Reporting Services LogViewer Tool Sample is developed in Microsoft Windows Presentation Foundation (WPF) in Visual C# using Microsoft Visual Studio 2010.

The sample demonstrates how to read and analyze the Reporting Services trace logs and the Report Server execution log data. The sample does the following:

  • Trace logs record report execution activity and the environment variables that are in effect during report processing. Errors and exceptions are also entered into trace logs. The sample helps us identify the frequency of the errors and exceptions logged in the trace logs.
  • Provide tips to fix any errors logged in Logfiles.
  • Describe the ExecutionLog columns, with tips on how to interpret values.
  • Interpret the ExecutionLog2.AdditionalInfo and some interesting pieces of information it provides.
  • Provide tips to analyze ExecutionLog2 information.
  • Provide tips to optimize reports.

You can download this tool from: http://www.microsoft.com/downloads/en/details.aspx?FamilyID=fd9031c2-2261-41f2-bf8e-fa1a00021450

Note: Supported DateTime format is MM/DD/YYYY from the SSRS Logfiles. This is how generally data is written to the SSRS Log files by default. If somehow you are trying to change the format of the DateTime to something else, the application will not be able to read the logs.

Any feedback/suggestions/comments regarding this tool is highly appreciated!!

Thanks..

Comments (8)

  1. JFoushee says:

    You are the creator the of LogViewer tool?

    Congrats on such a useful program!

    I did have a few suggestions.

    1. Allow the custom date ranges to include times. I was considering using this tool for troubleshooting purposes, but I only need the past two hours' worth of data. The "Today" option brings back too many results.

    2. Allow user to select a remote Trace file directory without having to map a network drive.

    3. Allow user to select multiple Trace file directories together. My company has installations of Reporting Services with multiple underlying nodes, containing independent trace logs.

  2. Great suggestions.. I am making a note of all the suggestions, and planning to include them in the next releases..

  3. JBallage says:

    Looks to be a very useful tool.  Do you plan to provide the source code on CodePlex?

  4. Thank you 🙂

    Not too sure as of now, but planning to do it via CodeGallery. Once its published, I will update my blog with the link. Hope that helps..

  5. Stephen Yale says:

    I would like to import the log file into SQL Server so I can compare log activity with perfmon traces. Can I parse the log into a SQL Server table?

  6. @Stephen: You can use this tool to import that log files. Once imported, use the export option to export it to any available formats like Excel. Once you have log files in Excel, you can use SQL Server Import/Export wizard for transfering data into SQL Server. Does that help?

    I dont know if you can directly import data from SSRS Log files into SQL Server, as they are in text formats.

  7. Can you share the code you used to parse the trace log files. I would like to bring them into SQL Server for analysis.

  8. Gordon Andersen says:

    Is there a way to modify or add to the list of embedded SQL Reports? I don't see any .rdl files that we can easily modify. But the front-end you've built is very intuitive and it would be powerful to be able to put this in the hands of some end-users too.