Log Parser Studio

Log Parser Studio is a utility that allows you to search through and create reports from your IIS, Event, EXADB and others types of logs. It builds on top of Log Parser 2.2 and has a full user interface for easy creation and management of related SQL queries.

4.6 Star
306,653 times
Add to favorites
E-mail Twitter del.icio.us Digg Facebook
  • Software Update
    6 Posts | Last post March 21, 2013
    • Out of curiosity, is this project still active and is an update in the works?
      Thank you!
    • Hi Nathanael,
      Yes, the project is still active and an udpate is in the works. The changes for the TSV issue below should also be in that update but I don't have a firm time-frame yet. Thanks!
    • i dont have a question, but to the developer of this, 
      THANK YOU!!! im going crazy with log parser, its a PAIN to use, 
      this is how tools are suppose to work!
      a big thx again, if any the only think i could request is a local to GMT time converter, other that that... EXCELLENT! why is this not default stock in the widows server admin tool?
    • Great...
    • Update: Its on the way. :)
    • @farid
      There are two time conversion functions if that may get you close:
      TO_UTCTIME( timestamp <TIMESTAMP> )
      TO_LOCALTIME( timestamp <TIMESTAMP> )
      Since they require a timestamp data type you may need the TO_TIMESTAMP() function:
      TO_TIMESTAMP( dateTime1 <TIMESTAMP>, dateTime2 <TIMESTAMP> ) | ( string <STRING>, format <STRING> ) ( seconds <INTEGER | REAL> )
      TO_LOCALTIME(TO_TIMESTAMP(date, time))
      TO_UTCTIME(TO_TIMESTAMP(date, time))
  • Unable to automate Batch Jobs
    2 Posts | Last post March 21, 2013
    • There appears to be a bug when trying to run batch jobs from the command line with a list of folders.  If I save an FLD file from the GUI I am unable to use them in a command line.  LPS opens and then displays the error "ExLPT.LPLogFile does not exist".  I noticed if I open the FLD file in a text editor and specify an individual log file it works fine. 
    • Thanks for finding this. I see the problem, it's an issue with passing folders using wildcards instead of individual files. It is choking on \*.log when verifying the files exist. I'm fixing now and will be in the updated release.
  • Log Parser Studio & SQL Functions
    3 Posts | Last post March 21, 2013
    • New to LPS (and like it) but am stuck on trying to figure out how to grab part of a field.  
      Querying on Date, Time, cs-username, s-ip, cs-uri-stem and cs-uri-query on a logfile folder.
      What I want to do is to just grab a portion of the cs-uri-query field to use in the query.  I thought the proper syntax would be:
      substring(cs-uri-query,17,8) or substr(cs-uri-query,17,8)
      but when I try that, I get an error that says:
      "Error parsing query:  Syntax Error: <field-expr>: cannot find a valid <field-expr>:'substring(cs-uri-query,17,8)' [SQL query syntax invalid or unsupported]"
      I'm certain that's how it functions in TSQL, and I'm able to do a LIKE on the portion of that field I'm trying to select, so I'm a little confused.  
      What am I missing?  Are there other SQL functions that do/don't work in LPS?
    • Log Parser 2.2 has similar but not always identical SQL type functions. However, SUBSTR()should work... 
      Try: SUBSTR( string <STRING>, start <INTEGER> [ , length <INTEGER> ])
      Example: SUBSTR(cs-uri-query, 0, 5)
    • A quick follow up that the Log Parser 2.2 manual has a complete list of Log Parser functions (there are quite a few of them). It is located in the directory Log Parser 2.2 was installed in. The default location is usually:
      C:\Program Files (x86)\Log Parser 2.2\LogParser.chm
      The latest version when released will also have a link directly to a function list.
  • Np Data from the Log Parser Studio
    2 Posts | Last post March 21, 2013
    • Also as mentioned in the document, there are no files located in the %AppData%\Microsoft\Log Parser Studio\LibraryName.XML ( in Appdata, i am looking at the LOCAL folder, not the ROAMING folder).
      Any advise on how get see the output ? I have just one log file ot look at to see if this works, but no luck until today.
    • You can change the CSV default output path in Options > Preferences > Default Output Path if I'm understanding the question. :)
  • No Data from the Log Parser Studio
    2 Posts | Last post March 21, 2013
    • Sorry Team..
      this became frustrating when i had installed log parser 2.2 and LPS on a Windows 7 64 bt machine and try to open an IIS activesync log but the output is blank. i have the right file type chosen.
      The same log file was opened by the Microsoft PSS engineer however it doesnt work on my machine... Please are there any pre-reqs for this tool. I have spent my last 10 hrs figuring out but no use ?
    • The only pre-req is .Net 4.0 and the complete install of Log Parser 2.2. Complete means that logparser.dll gets installed and registered which is part of the "complete" option in the installer.
      If I remember there is one ActiveSync query that shipped with a typo. I'm not in a place I can find it at the moment but will update when I do. If you can post the query or the name of the query you are running, I'll compare and reply.
  • Is there any update on upcoming versions?
    2 Posts | Last post March 21, 2013
    • I am using a custom log format with space separator and specific columns. It will therefore be very useful to be able to define custom log types.
      Any update on the TSV support?
    • The latest version is nearly ready. Currently, finishing up some new queries and there should be at least minimal support for modifying log type parameters AKA better TSV support.
  • Are there issues using LPS on HTTPERRR logs?
    3 Posts | Last post March 21, 2013
    • When I try to run a query against an HTTPERR log I get "Error parsing query: SELECT clause: Syntax Error: unknown field'cs-uri'.  The closest match for input format 'IISW3C is 'cs-uri-stem'. [Record filed dies not exist.]"
    • I am facing the same issue. HTTPERR log type is not recognized. When checking the LogType in the library xml file, the queries are configured with IISW3CLOG log type.
      @DCLF1, did you find a way to get it working?
      @Others, are httperr log files really supported?
    • There was a typo when setting the log type for most of the HTTPErr queries. Try loading the query, change the log type to HTTPErr, then save the query. That should fix it.
  • Great Tool, bat ...
    5 Posts | Last post March 22, 2012
    • When you run a query I get the following error:
      Unhandled Exception length cannot be less than zero
      See the end of this message for details on invoking 
      just-in-time (JIT) debugging instead of this dialog box.
      ************** Exception Text **************
      System.ArgumentOutOfRangeException: Length cannot be less than zero.
      Parameter name: length
         at System.String.InternalSubStringWithChecks(Int32 startIndex, Int32 length, Boolean fAlwaysCopy)
         at ExLPT.MainForm.queryTimer_Tick(Object sender, EventArgs e)
         at System.Windows.Forms.Timer.OnTick(EventArgs e)
         at System.Windows.Forms.Timer.TimerNativeWindow.WndProc(Message& m)
         at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
    • Hi Andrea,
      Try downloading again. The download contains an updated version that corrected this issue. Looking at the error above, this looks like the version that doesn't contain that update. I will download again myself to make sure the updated code is present. Let us know if you have further issues.
    • Wonderfull!! Now works well. Great tool.
      thank you.
    • Is this open source project? If yes, where I can find the source.
    • Good one..reports from IIS made really easy.
61 - 68 of 68 Items