Log Parser Studio 2.0 Released!
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.
https://blogs.technet.com/b/exchange/archive/2013/06/17/log-parser-studio-2-2-is-now-available.aspx
Direct link to the page with the latest bits:
https://gallery.technet.microsoft.com/Log-Parser-Studio-cd458765
The existing articles on LPS:
https://blogs.technet.com/b/karywa/
Comments
Anonymous
January 01, 2003
Hi Ross, 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. KaryAnonymous
January 01, 2003
Hi Jeff, That's a great point as Log Parser 2.2 only supports MD5 if I remember. Thanks for the comments! KaryAnonymous
January 01, 2003
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?Anonymous
January 01, 2003
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?Anonymous
January 01, 2003
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?Anonymous
January 01, 2003
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?Anonymous
June 18, 2013
Hi, it seems that when you sort by clicking the column header (instead of writing the proper ORDER BY) log parser 2.0.0.100 always sorts alphabetically. I.e 10 comes before 2,3,... Thanks for the great tool anyway :)Anonymous
June 18, 2013
Hi Jan, 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.Anonymous
June 23, 2013
The comment has been removedAnonymous
June 24, 2013
Hi Steve, 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.Anonymous
July 19, 2013
The comment has been removedAnonymous
July 22, 2013
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.Anonymous
September 20, 2013
The comment has been removedAnonymous
December 11, 2013
Hi Joshua, Are you still seeing this issue?Anonymous
June 02, 2014
The comment has been removedAnonymous
July 07, 2014
The comment has been removedAnonymous
September 22, 2014
The comment has been removedAnonymous
September 22, 2014
The comment has been removedAnonymous
September 22, 2014
The comment has been removedAnonymous
September 22, 2014
The comment has been removedAnonymous
September 22, 2014
Hi Ted,
I would need some type of explanation as to the steps taken to cause this. It looks like a legitimate bug but I need to know how I can cause the same error. Can you reliably reproduce and if so, please list the steps taken. I will try myself but if you know it would be a great help.Anonymous
September 22, 2014
My previous reply is concerning: System.InvalidOperationException: SplitterDistance must be between Panel1MinSize and Width - Panel2MinSize.Anonymous
January 21, 2015
I have had 2 issues.
1) If I have more than 10 columns in an XML file I end up losing one. It didn't matter which columns but as long as I had fewer than 11 I was OK. My strings values are not quoted. 10 can't be the limit. What am I missing here?
2) Assumption of datatypes....I ended up putting dummy string values in the first XML element, otherwise logParser studio assumed the datatype. In one case when I did leave the fist value empty it ignored all objects that had an unquoted string value that looked like a date. Is there switch to force all values be considered strings?
thanks so much.....BTW the GUI is great!Anonymous
February 17, 2015
@parsing XML issues
LPS simply passes on the query to LP 2.2 and the XML Log type in LP has always been a little difficult for me use efficiently. I would double check the LP 2.2 .chm/help file in the Log Parser 2.2 installation directory (if you haven't already) since that is all the info I currently have on the XML format for LP 2.2.Anonymous
November 22, 2016
The comment has been removed