Introducing: Log Parser Studio

The tool is fairly useful. I only use the IIS scripts to export to powershell, swap the SQL for my own requirements but there are a few bugs etc. Divide by zero is just one of them, null exception is another. One says about the double quotes being obsolete for the output com object.

As you use *.log, and filemode:0 (overwrite), it works but if you want to use a for/foreach loop, filemode needs to be changed to filemode:1 (append) and change the *.log to each log file name plus use ([math]::ceiling($i / $fileCount) / 100 )) in a for loop for the progress bar. $i is the current iteration and $fileCount are the total number of files

Also, exporting the scripts to Powershell and running are incredible slow when you use REVERSEDNS(c-ip). The queries I run can take 3 minutes but open Visual Studio 2022, create a windows app with a button using startupinfo, the same SQL query takes 1 second or less (including ReverseDns). So, swap the SqlQuery over from a script from LPS to run in Powershell is so slow running. We are talking 25 seconds or more per log.

Also, in IIS, create custom fields (X_FORWARDED-FOR etc) for logging then the scripts from LPS fail. If I leave an extended log in the directory and use LPS for a simple select/count and it fails, remove that file and it works again. Seems that the LPS needs some work.