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


  • Message Tracking - "Top Talkers by Sender" of the last hours
    1 Posts | Last post March 07, 2014
    • Hello,
      how can I modify the "Exchange 2010 Message Tracking: Top Talkers by Sender " Script, to get only Results of the last 4 hours?
      
      I dont know the syntax to realize it.
      
      I want to export ist to Powershell and schedule it, so that I can detect Auto Reply Loops and notify myself about it.
      
      Best Regards
      Christian
  • Common setting for all users
    1 Posts | Last post February 17, 2014
    • Hi. 
      I want to set up program settings common to all users on the server. How I can do that?
  • Parsing log4net logs
    1 Posts | Last post January 18, 2014
    • Hi, I am trying to find a way to parse log4net logs, but cant do that via LPS. 
      I tryed to use Log Parser Lizard and there I can specify xml which describe log file format. Unfortunatly LPL not free and I can't use it after trial. Can I do something like this in LPS?
      
      For example I have log with such format:
      INFO  [2013-12-01 00:55:24,268] [NIT.ClientWeb.Controllers.AccountController.Login] NIT.NIT.uk is Invoked at 12/1/2013 12:55:24 AM 
      
      and I can describe it with xml with regex like 
      
      <?xml version="1.0" encoding="UTF-8"?>
      <config xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="C:\src\LogParserCSWebServiceInputFormat\LogParserRegexInputFormat.xsd">
      	<regex>^(?&lt;LogType&gt;\w+)\s+\[(?&lt;DateTime&gt;(?:\d{4})-\d{2}-\d{2}\s\d{2}:\d{2}:\d{2},\d{3})\]\s+\[(?&lt;MethodName&gt;.*)\]\s(?&lt;Message&gt;.*)$</regex>
      	<fields>
                  <field name="LogType" type="String"/>
                  <field name="DateTime" type="Timestamp" format="yyyy-MM-dd HH:mm:ss,fff"/>
                  <field name="MethodName" type="String"/>             
                  <field name="Message" type="String"/>
      	</fields>
      </config>
  • Text Query text into sql table
    1 Posts | Last post December 17, 2013
    • Very useful, but how can I query text into sql table with sql parameter?
      Also , Log Type doesnot contain Sql.
  • Export Query as PowerShell script - problem
    2 Posts | Last post December 11, 2013
    • After choosing file name, the dialogbox is shown:
      Title: Export Library
      Message: Could not export to PowerShell:
               Object reference not set to instance of an object.
      How to resolve this problem?
    • Hi Victor,
      
      This has been fixed in the latest version: http://gallery.technet.microsoft.com/Log-Parser-Studio-cd458765
  • Application Error
    2 Posts | Last post December 11, 2013
    • Like Lazarus, I ran into this (interestingly, this did previously work).
      
      Backgroud thread error:one or more errors occurred.
      System.NullReferenceException: <InputFileFormatType>format returned null. The xml settings for this format may be corrupt or contain invalid entries.
      
      I clicked "Reset All Log Formats" in Options > Preferences. This reset my files in
      
      C:\Users\YourUserName\AppData\Roaming\ExLPT\Log Parser Studio\Config
      
      I also deleted these files and reset them.  I saw them come back after the reset.  I have tried to reinstall.  The logs work on another computer with LPS 2
    • Hi Lazarus/Diothar,
      
      I don't think this error can occur unless there is some permissions issue reading the config files. This of course should never happen on a normal system because all the config files are stored with in the user's profile. Additionally, if resetting them recreates them, I would think they can be read.
      
      I have seen this occur for one single internal user during the beta phase. I still suspect it is related to permissions and the user profile or similar. If I can repro this I can fix it but I have been unable to reproduce it thus far.
  • The specified checkpoint file is smaller than
    2 Posts | Last post December 11, 2013
    • Hello,
      I got the log parser 2.2 ran on window 2008 server for so many years.  Yesterday, the C drive was full.  After we clean and reclaim disk space, the log parser still give me an error "The specified checkpoint file is smaller than ".
      
      I got the file lpc file corrupted before, so I deleted the error_log.lpc but the problem still persist.
      
      I think about rebooting the server at mid-night.  Any idea?
    • Hi Diane,
      
      Check the properties for the IISW3C log type in LPS and make sure the iCheckpoint field is correct. I'm guessing it may have been previously set and the file it points to could be corrupted or the path itself is now incorrect. You might make sure it is blank and retry.
  • Advanced Logging for IIS
    2 Posts | Last post December 11, 2013
    • Hi,
      I'm using advanced logging for IIS which basically creates the same log file structure as the usual log, only with more available fields to choose from.
      I cannot use the IISW3CLOG parser because that parser assumes the existence of fields which are not part of my log.
      I tried W3CLOG by I get an error invalid cast exception (IISW3CINProperties to type W3CINProperties).
      I tried tabular separated file format, but it recognizes the "#fields" prefix as a column name, which requires me to manually edit each log file before analyzing it.
      
      Is there any planned support for custom fields in IIS logs?
      
      This is an example to the content of my file:
      #Software: IIS Advanced Logging Module
      #Version: 1.0
      #Start-Date: 2013-09-26 17:18:42.257
      #Fields:  CPU-Utilization W3WP-PrivateBytes s-port s-ip cs(User-Agent) cs-uri-stem cs-uri-query sc-status
      12.64 28733440 80 ::1 "Mozilla/5.0 (compatible; MSIE 10.0; Windows NT 6.2; WOW64; Trident/6.0)" /CPUThrottling/ - 200
      12.64 28733440 80 ::1 "Mozilla/5.0 (compatible; MSIE 10.0; Windows NT 6.2; WOW64; Trident/6.0)" /CPUThrottling/Scripts/jquery-1.8.2.js - 304
      12.64 28733440 80 ::1 "Mozilla/5.0 (compatible; MSIE 10.0; Windows NT 6.2; WOW64; Trident/6.0)" /CPUThrottling/Content/site.css - 304
      
    • Hi Ido,
      
      Fixed in latest version uploaded today:
      
      http://blogs.technet.com/b/karywa/archive/2013/12/11/log-parser-studio-v2-updated-12-11-2013.aspx
      
      http://gallery.technet.microsoft.com/Log-Parser-Studio-cd458765
  • Exported logs to third server
    2 Posts | Last post December 11, 2013
    • I have been using LPS, but  when I ran a query the EventCategoryName and Message, return:
      	EventCategoryName
      	The name for category 4 in Source "MSSQLSERVER" cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer"
      	Message
      	The description for Event ID 18454 in Source "MSSQLSERVER" cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer
      I used the command wevtutil al application.evtx and put both file and the LocaleMetadata folder under LPS  log folder . But If I check with eventvwr the query return all the information. Are there another procedure to export log? Thanks for your help
    • Hi JuansH,
      
      This sounds like the event information needed is on the remote machine but not the machine you are running LPS from. You can confirm by opening the exported EVTX file in Windows Event Viewer on the local machine that you are running LPS on and see if you see the same message.
  • Hi Kary,
    2 Posts | Last post December 11, 2013
    • Log Parser Studio does not seem to support IIS Advanced Logging.
      
      Here an example query with Log Parser that does work:
      
      LogParser.exe "SELECT SUBSTR(s-sitename, 0, INDEX_OF(s-sitename, ',')) as [SITENAME], date, time, s-ip, sc-status FROM 'C:\LogFiles\DEFAULT WEB SITE\*.log' WHERE (sc-status >= '400' AND sc-status < '500') ORDER BY sc-status" -i:W3C -dQuotes ON -o:datagrid
      
      The Log Parser Studio has several issues with this.
      1. Does not allow W3C (wan't to use IIS methods)
      2. Does not allow dQuotes ON for the W3C filter
      
      Maybe an good idea to install IIS together with the Advanced Logging module to reproduce the issue and get it to work with the studio, unless you already got a quick fix that you can share here. :)
    • HI Joerg,
      
      The latest version supports IIS Advanced Logging:
      
      http://blogs.technet.com/b/karywa/archive/2013/12/11/log-parser-studio-v2-updated-12-11-2013.aspx
      
      http://gallery.technet.microsoft.com/Log-Parser-Studio-cd458765
31 - 40 of 66 Items