SQL Server Reporting Services (SSRS) HTTP Log Files cannot be parsed

I have been unsuccessful parsing HTTP Logs from SQL Server Reporting Services (version 2008 R2). I have followed the Microsoft instructions at http://msdn.microsoft.com/en-us/libra... to enable HTTP logs for reporting services, and logs are indeed created. According to this website, "The Report Server HTTP log file is equivalent to the W3C extended log file in IIS and uses similar fields so that you can use existing IIS log file viewers to read the report server HTTP log file".

In WebLog Expert I get the message "The analyzed log files don't contain any information, which can be analyzed by the program". The profile does not have any filters or ignore lists, and the Time Range I've specified is All Activity, so from what I gather, the only possible reason is the format.
Any experience with this type of file?

Here's a sample from the resulting file:
#Fields: date time c-ip cs-username s-ip s-port cs-method cs-uri-stem cs-uri-query sc-status cs-bytes time-taken cs(User-Agent)
12/06/2012 17:55:12 192.168.113.183 - 192.168.201.115 20480 GET /ReportServer/Pages/ReportViewer.aspx ?/Test%20Reports/TestReport 401 465 0 ssrsserver
1 person has
this question
+1
Reply
  • The issue appears because the date has unusual format (mm/dd/yyyy) in the log. According to the W3C Extended formats specifications date must have the yyyy-mm-dd format like in IIS logs. As the result, WebLog Expert cannot read the log.

    Unfortunately, it's not possible to setup WebLog Expert to recognize logs in this format. It may be only possible to analyze them if dates in the log will be fixed using an external tool, or if it will be possible to setup SSRS to use another date format (while it seems that there is no such option available).
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. happy, confident, thankful, excited indifferent, undecided, unconcerned sad, anxious, confused, frustrated kidding, amused, unsure, silly