Error Opening Event Log
Contents |
Without the Cruft: Windows 10 LTSB (Long Term Servicing Branch), Explained Subscribe l l FOLLOW US TWITTER GOOGLE+ FACEBOOK GET UPDATES BY EMAIL Enter your email below to get exclusive access to our best
Opening Event Viewer
articles and tips before everybody else. RSS ALL ARTICLES FEATURES ONLY TRIVIA Search opening event viewer and viewing events related to failover clustering How-To Geek Fixing "Event Viewer cannot open the event log" When Viewing System Logs As any geek knows, one of the first opening event viewer from command line things that you do when troubleshooting a Windows problem is look into Event Viewer's Application or System logs, which typically are rich with information on what the problem is. But what if the event log itself is
Application Event Log Location
corrupted? I came across this exact situation the other day, where I was getting the error "Event Viewer cannot open the event log or custom view. Verify that Event Log service is running. The data is invalid (13)"… but the error only happened when trying to open the System log, while the Application log was working just fine, and restarting Event Log or rebooting didn't help. What you can do in this situation is
Event Viewer Cannot Open The Event Log Access Is Denied (5)
clear the system log, saving it to a file in the process. This will usually "reset" the log so that future events will be viewable. Clearing the System Log Here's an example of the error message that I've been getting: You can right-click on any of the logs and choose "Clear Log" from the menu. You'll want to choose "Save and Clear" when prompted just in case you need to access those events. Give the logfile a useful name, and then click the Save button to continue. Note that you probably won't be able to open the log with Event Viewer, but you could open it in a text editor and try and find some information in it. Now that I've cleared the log, you can see that I'm able to view the events in the System log again.
Extra Note: The problem I was encountering ended up being because I had 9 USB devices plugged into a machine with a very pathetic power supply. Moving the devices onto a Powered USB hub fixed the problem, and I've since upgraded the power supply. JOIN THE DISCUSSION Tweet Lowell Heddings, better known online as the How-To Geek, spends all his free time bringing you fresh geekery on a daily basis. You can follow him on Google+ if you'Service not starting RECOMMENDED: Click here to fix Windows errors and improve system performance Windows Event Log service maintains a set of event logs that the system, system components, and applications event viewer cannot open the event log or custom view. verify that event log service is running use to record events. The service exposes functions that allow programs to maintain
Windows Could Not Start The Windows Event Log Service On Local Computer Error 4201
and manage the event logs and perform operations on the logs, such as archiving and clearing. As such, administrators can windows could not start the windows event log service on local computer error 5 access is denied maintain event logs and perform administrative tasks requiring administrator privileges. Windows Event Log Service Not Starting or Running For some unknown reason if you find you are having difficulty starting the following, it http://www.howtogeek.com/howto/windows-vista/fixing-event-viewer-cannot-open-the-event-log-when-viewing-system-logs/ is quite possible that one of the reason could be that Windows Event Log Service is Not Running. Task Scheduler Windows Event Calendar Messenger Sharing Folders In such a scenario, you may get error messages like: Event Log service is unavailable. Verify that the service is running Windows could not start the Windows Event Log service on Local Computer First, reboot your system and see if http://www.thewindowsclub.com/windows-event-log-service-not-starting it helps. Sometimes a simple restart helps reinitialize this service. If the Windows Event Log shows as being started, re-start it from Services Manager. To check if the Windows Event Log service is started or stopped, Run services.msc and hit Enter to open the Services Manager. Here, again right- click on Windows Event Log Service, check up its Properties. Ensure that the Startup type is set on Automatic and that the services is Started; and that it runs in the Local Service account. Advertisement ^ Also ensure in the Recovery tab, all three drop down boxes, show the option as ‘Restart the Service', in case of Failure. Reboot if required. At times the Windows Event Log Service still will not start, and you may instead get the following error message: System cannot find the file specified In this case, open the following folder: C:\Windows\System32\winevt\Logs This logs folder contains Event Logs in .evtx format and can only be read with the Event Viewer. Give this logs folder Read-Write access rights and see if it helps. You might also want to do the following. Open Registry Editor and navigate to the following key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\eventlog Double-click ObjectName
6 Joined: 11/30/2007 Status: offline Error opening event log file Wednesday, January 16, 2008 7:24 PM (permalink) Hello I installed gfi EV and he added http://forums.gfi.com/Error-opening-event-log-file-m900758552.aspx a machine (xxx.xxx.xxx.xxx) use customer account management enable remote registry and where is the treatment of GFI scan this machine and get the message Erro opening event log application on machine xxx.xxx.xxx.xxx Any help will be welcome #1 Looking4Answers Total Posts : 38 Joined: 11/24/2006 Status: offline RE: Error opening event log file Thursday, January 17, 2008 event log 2:18 AM (permalink) Verify the account credentialsthatare being used when connecting to machine (xxx.xxx.xxx.xxx)have access to this system. You should be able to verify the account being used in the Security logs of the destination system as well as the configuration of GFI.You may also want to check and make sure the Application LogFile is not corrupt. Your might want to add more opening event viewer information for the GFI technicians as well. The turn around on the message board is typically 12-24 hours at a minimum. #2 Mark Busuttil Total Posts : 4836 Joined: 10/17/2005 Status: offline RE: Error opening event log file Thursday, January 17, 2008 3:04 PM (permalink) Hi, Can you also please perform the following test: 1. Start > Run > Eventvwr 2. Right Click on Event Viewer (Local) > Connect to another Computer 3. Enter the IP address or machine name within Select Computer Diaglogue. Can you please confirm if you are able to browse through the remote machines Event Logs in this way? Thank you! Regards, Mark Busuttil GFI Software Ltd - www.gfi.com Messaging, Content Security & Network Security Software GFI: MailEssentials - MailSecurity - MailArchiver - FAXmaker - LANguard – WebMonitor #3 Fred_pro Total Posts : 6 Joined: 11/30/2007 Status: offline RE: Error opening event log file Thursday, January 17, 2008 11:46 PM (permalink) Hello I used the account of the administrator of the machine remotely, it is assumed that this has all the privileges I have, b