After quite a bit of blood, sweat and tears, LPS 2.0 was released today. A large number of improvements have been made since V1. When considering improvements many were the result of either feedback from engineers and customers or, removing workflow barriers whenever I ran into them. In other words since I use LPS everyday I inevitably hit something that makes me think "well that could be easier than it is" which led attempting to meet that need, OK that's better, rinse and repeat.
This means that many times I was running LPS in debug mode in the Visual Studio 2012 development environment. If I stumbled across something that could be a little better, I could make the change right then and there. So, there was a good bit of refinement based on day to day use which I hope will provide the same value to you.
I'll be posting many of these improvements along with their explanations in the very near future so be sure to keep checking back as there will be goodies abound. :) In the meantime, check out the EHLO article, download LPS 2.0, check out the existing articles to experience some of the new stuff: Here is the EHLO article.
Direct link to the page with the latest bits:
The existing articles on LPS:
it seems that when you sort by clicking the column header (instead of writing the proper ORDER BY) log parser 220.127.116.11 always sorts alphabetically. I.e 10 comes before 2,3,...
Thanks for the great tool anyway :)
Enable "Make columns sortable" in preferences and you can sort properly. Its disabled by default because columns with differing data types may cause issues. As long as the column contains the same data type (such as only numbers or only text) it should sort as expected.
Nice job on this! Thanks for creating a second version. I thought any work using LogParser was halted, which was a bit disappointment, as I created a few web apps using the Classic ASP and COM, thought it was one of those swiss army tools in a niche where it was badly needed. I had heard a while back there was going to be some replacement, which I am sure was going to be .NET based. I have not seen anything yet.
I work in WebMetrics, sysadmin and databases, so I have been staring as logs and especially IIS and Apache logs for 15 years. I was using the typical CygWin *nix command like grep, se, awk, find etc.
I only have one nit-picky issue - the escape key does not work on dialogs. Maybe I am spoiled, but I always thought that was the default behavior of modal dialog...??
Agreed and challenge accepted. :) so I'll see if I can get the escape feature in at some point. I'll likely gather suggested changes/bugs for a short time then make all the changes in a single future update.
I love Log Parser and LPS! One thing I wish Log Parser had was the ability to hash files with hashing mechanisms other than just md5 (such as SHA1, SHA256) I'm not sure if the developers would be interested in adding that feature, but it would be great as you might have other hash types that you need to compare. Also, it would be great if hash generation was done for only those files that meet all the criteria (except hash comparisons) in the "where" clause given the processing impact of generating hashes. I think that would boost performance of file hashing using Log Parser.
That's a great point as Log Parser 2.2 only supports MD5 if I remember.
Thanks for the comments!
I'm having issues with urlscan logs and LPS - I've found a bit of a work around which seems ok (stackoverflow.com/.../17788184)
just wondering if there is a better way? Apart from that, great work on LPS.
That is the correct way to do it. Those settings will be saved with the TSV log format (albeit globally) so the next time you query a URLScan log you should be good to know. Let me know if you have any other questions.
I'm running into a situation where LPS2 no longer works.
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
Are you still seeing this issue?
This is awesome. But I couldn't use LPS on SharePoint ULS logs. Do you know which LogType I need to select to parseSharePoint ULS logs?
I tried to edit my comment after I posted and realized I couldn't do it. I figured out TSV format would work for SharePoint ULS logs but surprisingly not all fields are picked by LPS. For instance column Message was pciekd up but column User was not picked
up. Am I missing something?
Kary Wall: Apologies if I'm spamming your beautiful post. I figured out what I was missing. The 'User' field was never in the ULS logs though it displays in the ULS viewer. apparently it was functionality of ULS Viewer. One last query: If I try to print
entire stack trace from my log files, I find that LPS is truncating the information after certain length. IS there a limit on the length of the column that LPS can retrieve/display?
Hi Kartik, I'm unaware of such a limitation so, can you tell me how many characters are in the stack trace and or a sample query and I'll try the same against a ULS log?
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.]
hresult Exceplnfo& exceplnfo, U1nt32 argErr, String message)
at CallSite.Target(Closure, CaIlSite, ComObject, String)
Site site. TO argO, Ti argi)
at CalISite.Target(Closure, CaIlSite ...
Message Tracking: Exchange 2010- Top Talkers by Sender/Send Source
Any assistance would be highly appreciated.