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.

LPSV2.D2.zip
 
 
 
 
 
4.6 Star
(138)
302,907 times
Add to favorites
Exchange
12/12/2014
E-mail Twitter del.icio.us Digg Facebook
Sign in to ask a question


  • Exchange2013
    2 Posts | Last post April 20, 2015
    • is is compatible with Exchange 2013
    • It is but the log types may vary (EEL, EELX, EWS, RPCA) etc. In other words there may be queries that were originally written for Exchange 2010 that may not work properly for Exchange 2013 logs but it depends on the protocol/log. Of course it is fully compatible when constructing your own queries.
  • COM Plug-In Support
    2 Posts | Last post April 20, 2015
    • Are there any options to support custom COM plug-in support for other log formats?
    • The question has come up but I haven't found a workable solution just yet.
  • Excellent
    2 Posts | Last post August 19, 2014
  • ADD or + functions
    1 Posts | Last post July 17, 2014
    • I'm trying to write my own query dealing with total bytes/kb/mb received and sent in IIS logs. I've got it working except for one thing. I want to add a final piece of data to select for which is the total mb handled (sent and received). I've tried to sum the SUM results of the two columns (sc-bytes and cs-bytes) with SUM, ADD, and + but have gotten errors with all of the attempts. Kary can you please help?
  • What about -iCOM option ?
    1 Posts | Last post June 20, 2014
    • Is it possible to use the COM plugin functionality provided by LogParser ? (I didn't manage to figure out how to do it with LPS 2.2)
      
      It might be an interesting addition, to parse some custom log files for example
  • Source Code
    1 Posts | Last post June 20, 2014
    • Any chance of releasing the source code for Log Parser Studio? 
      A GitHub or CodePlex repository perhaps? 
  • Windows 2012 R2 and Window 2008 R2 supporting version??
    1 Posts | Last post May 22, 2014
    • When I have installed logparser studio on Windows 2012 R2 and Window 2008 R2 and mapping some log files to parse, getting error message while executing any query. I tried it on 3 machines, 2 win2012 R2 and 1 win2008R2, no luck.
      
      Error message is: 
      
      Background thread error One or more errors occurred.
      System.Runtime.lnteropServicesCOMException (OxSOO7000D): Error
      setting property icheckpoint: Invalid value for parameter
      icheckpoint” [The data is invalid.]
      at System.Dynamic.ComRuntimeHelpers.CheckThrowException(1nt32
      hresult Exceplnfo& exceplnfo, U1nt32 argErr, String message)
      at CallSite.Target(Closure, CaIlSite, ComObject, String)
      at
      System.Dynamic.UpdateDelegates.UpdateAndExecute2[T0,T1,TRetJ(Call
      Site site. TO argO, Ti argi)
      at CalISite.Target(Closure, CaIlSite ...
      Message Tracking: Exchange 2010- Top Talkers by Sender/Send Source
      EELLOG
      
  • This is awesome!
    1 Posts | Last post April 15, 2014
    • I love LogParser, and this is a great addition to it!
  • Compare two CSV files
    1 Posts | Last post April 03, 2014
    • Is it possible to compare two csv files with Log Parser?  I know it is possible to parse for missing fields but is it possible to compare differences in the CSV File?
      
      I know this works:
      SELECT
          SamAccountName,
          LastLogonTimeStamp,
          Group
          WhenCreated,
          PasswordNeverExpires,
          AccountExpires,
          Description
      INTO
          finalnew.csv
      FROM
          new.csv
      WHERE
          SamAccountName NOT IN
          (SELECT SamAccountName
           FROM master.csv)
      What if I wanted to check if the group name was different in one of the files?  What SQL strings would I use?
  • Parsing IISW3CLOG format (Issues)
    2 Posts | Last post March 26, 2014
    • Have been running queries to calculate bandwidth used/served per month and received mixed results far lower than expected, some with _negative_ values.
      
      Running the same query in LogParser itself yields the correct results.
      
      My guess is that some log files don't have cs-bytes and sc-bytes (default log format in IIS doesn't include these) and LogParserStudio is perhaps not honoring the headers if they're 
      
        a) different in subsequent files 
        b) redefined inside the same log file
      
      
      Query used was:
      
      SELECT 
        TO_LOWERCASE(cs-host) as host, 
        TO_INT(TO_STRING(TO_DATE(Date), 'yyyy')) AS year,
        TO_INT(TO_STRING(TO_DATE(Date), 'MM')) AS month,
        count(*) as hits,
        sum(cs-bytes) as inbytes, 
        sum(sc-bytes) as outbytes
      from '[LOGFILEPATH]'
      group by 
        cs-host, 
        TO_INT(TO_STRING(TO_DATE(Date), 'yyyy')), 
        TO_INT(TO_STRING(TO_DATE(Date), 'MM')) 
      order by 
        host, year, month
      
      
      PS: I couldn't find any other place to submit this - seems like a great GUI extension to an already great tool.
    • Hi dtrans,
      
      I'll have to try to test this. LPS simply tries to hand the query off to LP 2.2. I'm guessing the same as you where the first time the header is encountered it is set there and subsequent one's may get ignored. I'll try to see if I can find the best answer. However, this is the best place to submit questions, or my blog where there are a number of LPS articles. http://blogs.technet.com/b/karywa/
21 - 30 of 66 Items