Microsoft Exchange ActiveSync (MAS), Exchange Web Services (EWS), Outlook Web App (OWA/HTTP) and others. Once you launch it, you’ll notice tabs for different Exchange protocols, i.e. Log Parser Studio is mainly designed for quick and easy processing of different logs for Exchange protocols. You can also use special purpose scripts that one can find on the web and then analyze the output to make some sense of out of those lengthy logs. You also need expertise in writing those SQL queries. In the absence of special purpose tools, it becomes a tedious task for an Exchange Administrator to sift thru those logs and process them using Log Parser (or some other tool), if output format is important. We all know this very well: processing logs for different Exchange protocols is a time consuming task. We can search for queries using free text search as well as export and import both libraries and queries in different formats allowing for easy collaboration as well as storing multiple types of separate libraries for different protocols.

We can edit and create new queries in the ‘Query Editor’ and save them for later. With Log Parser Studio ( LPS for short) we can house all of our queries in a central location. Log Parser Studio was created to fulfill this need by allowing those who use Log Parser 2.2 (and even those who don’t due to lack of an interface) to work faster and more efficiently to get to the data they need with less “fiddling” with scripts and folders full of queries. The only thing missing is a great graphical user interface (GUI) to function as a front-end to Log Parser and a ‘Query Library’ in order to manage all those great queries and scripts that one builds up over time. In addition, adding the power of SQL allows explicit searching of gigabytes of logs returning only the data that is needed while filtering out the noise.

To download the Log Parser Studio, please see the attachment on this blog post.Īnyone who regularly uses Log Parser 2.2 knows just how useful and powerful it can be for obtaining valuable information from IIS (Internet Information Server) and other logs.

Msert log file location