Ken H.
asked on
Convert .evt to txt file or csv ..... or anything else I can actually read
I am building a web application that needs to parse event logs that have previously been collected and are saved as .evt files.
While I have found a way to read the system I am on, or even a remote systems event logs through vb.net i find no way to simply read an event log that was saved in the .evt format.
So now my question is how can I convert these saved .evt files that are from remote servers. Note these are client machines so I have no way to collect or convert these via powershell. I need a way that accepts the saved evt file and outputs a csv file ideally. I have been playing with Logparser but have been unable to figure out how to convert files that are not the actual systems event logs. Any help would be greatly appreciated.
While I have found a way to read the system I am on, or even a remote systems event logs through vb.net i find no way to simply read an event log that was saved in the .evt format.
So now my question is how can I convert these saved .evt files that are from remote servers. Note these are client machines so I have no way to collect or convert these via powershell. I need a way that accepts the saved evt file and outputs a csv file ideally. I have been playing with Logparser but have been unable to figure out how to convert files that are not the actual systems event logs. Any help would be greatly appreciated.
SOLUTION
membership
Create a free account to see this answer
Signing up is free and takes 30 seconds. No credit card required.
SOLUTION
membership
Create a free account to see this answer
Signing up is free and takes 30 seconds. No credit card required.
ASKER CERTIFIED SOLUTION
membership
Create a free account to see this answer
Signing up is free and takes 30 seconds. No credit card required.
>>quotes around the select statement was not in the manual
All the help file examples show quotes around the select statement. Where were non-quoted examples?
All the help file examples show quotes around the select statement. Where were non-quoted examples?
ASKER
In the form field entry syntax. Someone else provided me with the correct command line function to do what I was looking for. I gave you 100 points because you took a minute to google the question, but I had already googled it, over and over, and I already previously stated I was trying to work with log parser. Your post didn't assist me in obtaining an answer to my problem.
@newimagent
I wasn't trying to get more points. I was going to let Microsoft know about a deficiency in their Log Parser documentation.
You are correct, that my posted links came from a Google search. This question is in a couple of programming zones and while you had posted that you had been "playing with Logparser", it wasn't clear that you were using the Microsoft utility.
>>or convert these via powershell
>>files that are not the actual systems event logs
You were playing with PowerShell and had raised the possibility that these .evt files might not be in a (standard) format that was acceptable to the 'flavor' of Logparser utility you had tried.
I wasn't trying to get more points. I was going to let Microsoft know about a deficiency in their Log Parser documentation.
You are correct, that my posted links came from a Google search. This question is in a couple of programming zones and while you had posted that you had been "playing with Logparser", it wasn't clear that you were using the Microsoft utility.
>>or convert these via powershell
>>files that are not the actual systems event logs
You were playing with PowerShell and had raised the possibility that these .evt files might not be in a (standard) format that was acceptable to the 'flavor' of Logparser utility you had tried.
ASKER
Is the answer I was looking for. quotes around the select statement was not in the manual :/