All Tags >
Microsoft Log Parser Toolkit, the book (
RSS)
Sorry, but there are no more tags available to filter with.
-
[QUOTE User="LogParser User : Kou"]Quote: I'm sorry, I completely missed the important bits of the issue. You have two problems. 1. Your number is the number of milliseconds 2. Your number is based on the unix epoch (1970) instead of the SQ...[/QUOTE] Hi Daniel, Thanks a ton for ur reply, now i could...
-
I'm sorry, I completely missed the important bits of the issue. You have two problems. 1. Your number is the number of milliseconds 2. Your number is based on the unix epoch (1970) instead of the SQL epoch, (0000). You can overcome the first problem by dividing by 1000. LogParser's TO_TIMESTAMP() can...
-
[QUOTE User="LogParser User : Kou"]Quote: Read the help file and look for the time conversion functions. TO_STRING(mytime, 'dd-MM-yyyy hh:mm:ss') might work for you..[/QUOTE] Thanks for ur reply Daniel, I tried with the following query, C:\Program Files\Log Parser 2.2>LogParser "Select TO_STRING(time...
-
Read the help file and look for the time conversion functions. TO_STRING(mytime, 'dd-MM-yyyy hh:mm:ss') might work for you..
-
Hi I am using Logparser to convert XML file data to XLS file. I am getting the Time in milliseconds. I want this time to be displyed in "dd-MM-yyyy hh:mm:ss" format. If you have any suggestions, let me know.
-
OH! I understand now! I thought you blew away the query and were left with just a nearly empty file with "FROM System" in it. The real problem is that you need to prepend the filename of the query with file: when you are running LP with a query file instead of a query on the command line. That sentence...
-
This is the code I ran that gave me the error mentioned above: SELECT TO_LOWERCASE(EXTRACT_TOKEN(Strings,0,'|')) AS Account, SUM(CASE EventType WHEN 16 THEN 1 ELSE 0 END) AS Failed, SUM(CASE EventType WHEN 8 THEN 1 ELSE 0 END) AS Success, COUNT(*) AS Total FROM Security WHERE EventCategory=2 AND EventID...
-
By " just FROM Security not Security.evt " I meant that the .evt part was causing LP to look for a file named Security.evt instead of querying the active System event log. This is your query changed to fix the FROM clause: SELECT TO_LOWERCASE(EXTRACT_TOKEN(Strings,0,'|')) AS Account, SUM(CASE EventType...
-
I changed it to just FROM Security and I get the following error: C:\Program Files\Log Parser 2.2>logparser.exe UserLogins.sql Error: Syntax Error: <select-clause>: no SELECT keyword
-
Just FROM Security not Security.evt.