Cannot Open From-entity Error Opening Event Log
Web Platform Installer Get Help: Ask a Question in our Forums More Help Resources Blogs Forums Home IIS.NET Forums Logparser Forums General Discussion Solution to: Error reading event log: The event log file is corrupted... Solution to: Error reading event log: The event log file is corrupted. [Answered]RSS 1 reply Last post Apr 14, 2008 05:08 AM by Zhao Ji Ma - MSFT ‹ Previous Thread|Next Thread › Print Share Twitter Facebook Email Shortcuts Active Threads Unanswered Threads Unresolved Threads Advanced Search Reply foxR 2 Posts Solution to: Error reading event log: The event log file is corrupted. Apr 08, 2008 06:36 AM|foxR|LINK When I tried to read a large application event log file, I got that message. After clearing the log file, the problem was gone. Does anybody know limitations on size of the different resources (my application event log was 247MB) ? Reply Zhao Ji Ma -... 762 Posts Re: Solution to: Error reading event log: The event log file is corrupted. Apr 14, 2008 05:08 AM|Zhao Ji Ma - MSFT|LINK Hi, The file size 247MBof event log is fine for LogParser. If you are running LogParser from Windows Vista for old format of event log file which has file extension of .evt, you may experience "The event log file is corrupted." error. Task aborted. Cannot open
Stewart -MSFTAugust 31, 20078 0 0 0 I am a frequent user of LogParser and when I recently started using Windows Server 2008 beta as my desktop OS I ran into a problem with it. One of the things I use LogParser for is extracting the information I need from my customers' event logs which are often quite large and usually from Windows Server 2003. So I got a surprise when I first tried to do this on Longhorn: Logparser -i:EVT "select * from application.evt"Task aborted.Cannot https://forums.iis.net/t/prev/1148719 open
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this http://stackoverflow.com/questions/14143980/logparser-error-syntax-error-extra-tokens-after-query-files-apache site About Us Learn more about Stack Overflow the company Business Learn more about hiring developers or posting ads with us Stack Overflow Questions Jobs Documentation Tags Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow is a community of 4.7 million programmers, just like you, helping each other. Join them; it only takes a minute: Sign up LogParser Error: Syntax cannot open Error: extra token(s) after query: 'Files\Apache' up vote 1 down vote favorite 1 I am trying to run LogParser to dump all contents from access.log into an equivalent CSV file: C:\Program Files\Log Parser 2.2>LogParser "select * into foo.csv from C:\Program Files\Apache Software Foundation\Apache2.2\logs\access.log" -i:ncsa -o:csv However, I keep getting this error: Error: Syntax Error: extra token(s) after query: 'Files\Apache' and I am unsure of cannot open from-entity whether I am missing more syntax or I have some format wrong. apache logparser share|improve this question asked Jan 3 '13 at 17:25 Angry Spartan 1,49952857 add a comment| 2 Answers 2 active oldest votes up vote 1 down vote I'm not familiar with log parser, but judging from the error, your query is terminating at the first space. The site: http://misigah.com/?p=28 mentions using "\u0020" for spaces within a query column. Following that guidance, your query would be: *LogParser "select * into foo.csv from C:\Program\u0020Files\Apache\u0020Software\u0020Found...* There is also 2 spaces between "Program" and "Files". Hope that helps share|improve this answer answered Jan 3 '13 at 17:54 Kevin Whatever 1847 The extra space did give me a slightly different error, but that was a good catch. However, adding those hardcoded spaces you mentioned did not help. I got a new error: Cannot open