Log Parser Studio V2 Updated (12/11/2013)
The latest bits for LPS 2.0 are now available. This update contains a number of small fixes and enhancements including the promised fix of enabling the "Use Double Quotes" option for IIS Advanced Logging. The latest bits and associated links are below.
Download the latest version of LPS:
https://gallery.technet.microsoft.com/Log-Parser-Studio-cd458765
There is also the ability to query Dynamics CRM logs. The log type is listed as "CRMLOG" in LPS. For more information see the following link.
https://support.microsoft.com/kb/907490
Change List
+ Added custom support for Dynamics CRM tracing.
+Added default backslash to iCheckPoint for CSV because null
crashes PS export for CSV.
+Fixed chart type dropdown focus issue.
+Rewrote InputFormat parsing so that we derive the actual
name instead of [name, {type}] etc.
+Enabled IISW3C double quotes for IIS Advanced Logging. *** (Update - There is an issue with this fix which is being investigated. In the interim please use the workaround found here.)
+Added Accept/Cancel buttons for Enter/ESC .
+Fixed PowerShell "tabs" param issue.
+Removed ValueFromPipeline from PS Script Template.
+Added Accept/Cancel buttons for Enter/ESC.
+Added cancel buttons/ESC functionality to format dialogs.
+Updated FunctionReference.html
+Added queries for ActiveSync Troubleshooting Guide
Walkthrough (Ref: https://support.microsoft.com/common/survey.aspx?scid=sw;en;3616&showpage=1)
+Multiple small fixes/improvements/enhancements
Comments
- Anonymous
January 01, 2003
I fixed, it, let's hope I didn't break it without realizing it. Let me go back and do some testing and I'll follow up. Can I assume that you have "use double quotes" enabled now and it still doesn't work? - Anonymous
January 01, 2003
Hi James,So you did enable "Use Double Quotes" in the properties for the IISW3LOG type? Last time I tested this worked with Advanced Logging. If you are still having issues there is a workaround here that you can try while I investigate: http://blogs.technet.com/b/karywa/archive/2013/06/28/log-parser-studio-and-iis-advanced-logging.aspx - Anonymous
January 01, 2003
I would love to see intellisense and the ability to export the query to the clipboard to paste into the command prompt. These are 2 of the features that I love in the Log Parser Lizard by Lizard Labs. - Anonymous
January 01, 2003
Couple of stupid questions:1) where is the "FunctionReference.html" file located2) How do you display your "Favorite" queries? - Anonymous
January 01, 2003
The comment has been removed - Anonymous
January 01, 2003
FunctionReference.HTML = SHIFT+F3For favorites: Options > Preferences > Enable legacy category buttons - Restart LPS. Favorites is the Star shaped button on the far right. You can also find the function reference in the LP 2.2 .CHM in program file (x86)Log Parser 2.2 - Anonymous
January 01, 2003
Hi Steve, we have typically been using the case statement. See "Active Sync Report" query to see just how long these can be and still work quite well (other than the time it takes to enter them). If I find a better method I'll update. - Anonymous
January 01, 2003
Hi Bjorn,
Creating a custom type is possible but it would have to be compiled into LPS before it would see it. You can however, use TextLine Log Type and do some pretty fancy stuff. If you press Shift+F12 in LPS you'll get LP 2.2s function list which you can use to dig out just about anything you want. - Anonymous
January 01, 2003
The comment has been removed - Anonymous
January 15, 2014
The comment has been removed - Anonymous
January 23, 2014
The comment has been removed - Anonymous
January 24, 2014
The comment has been removed - Anonymous
February 11, 2014
Hi, Last december, Kary wrote that LPS will support custom fields in IIS logs in the next version, but it seems that it still not works. Or do I something wrong? Thanks for help, Clay - Anonymous
March 24, 2014
I'm also having problems given a custom field on my IIS advanced log. An update? - Anonymous
May 07, 2014
First of all - great tool! I am curious though if it is possible to define my own log types. I am trying to develop a solution which will parse many proprietary log where errors sometimes span multiple lines which I would like to group somehow. I figure that the most logical solution would be to create a custom log type for each log I will be parsing - is this possible? - Anonymous
August 08, 2014
LPS complains that I need to install .NET 4.0 when I launch lps.exe on my Windows 7 / .NET 4.5 environment. I have mandatory corporate apps installed that require .NET 4.5. My research tells me that 4.0 and 4.5 cannot run side by side. Are there any tweaks required to run LPS in a .NET 4.5 environment (perhaps I've missed something obvious)? Any workaround (short of running in a dedicated VM) would be appreciated. - Anonymous
September 22, 2014
Hi James, I'm not sure why it would be complaining. I'm running it on .NET 4.5. They can't run side by side but 4.5 should be able to run 4.0 apps. - Anonymous
February 02, 2015
Hi Kary -- thanks for this tool and the posts about it! It's a great resource. Is Microsoft / are you interested in potentially making this project open-source? I would love to understand the workings of this and see if I couldn't contribute something as well. If you're interested, shoot me an e-mail at SeanKilleen@gmail.com or on twitter at @sjkilleen. - Anonymous
February 04, 2015
I am using log parser on an IIS Advanced Logging file using the w3C format. I have a custom field with the client header IP address. When I run my query i am getting the wrong fields returned to me. For example I query out s-computer name and I get cs-version instead. Any idea what's going on and how I can fix it? - Anonymous
February 17, 2015
Just another voice for the issues with Advance logging. I couldn't get the workaround to function properly with 2.2 (though I might not have tried hard enough). A shame as this tool seemed pretty much what I was looking for to generate some custom queries and have them generated some basic graphs. (I have programmed my own queries in LinqPad prior, but this seemed to same a lot of time.) - Anonymous
February 17, 2015
The comment has been removed - Anonymous
February 17, 2015
@Matthew, The workaround requires a manual header file that determines the field names. Are we sure those are both correct and aligned in the proper order? - Anonymous
February 24, 2015
The comment has been removed - Anonymous
March 04, 2015
The comment has been removed - Anonymous
October 30, 2015
Hi James,
I'm not sure I understand. Anytime you use an aggregate function, in this case Count(*), you must include all non-aggregate fields, in this case c-ip and LocalTime in the GroupBy clause.
In the above query --comment tells LPS to ignore it and everything that comes after it hence the wording of the error. What am I missing?
Feel free to report anything you wish in this article and I will reply as soon as I can.
Kary - Anonymous
May 17, 2016
Functions such as Count(*) Require group by for each field that isn't a function.Thanks!Kary