Event Log Error 3
Contents |
be down. Please try the request again. Your cache administrator is webmaster. Generated Sat, 15 Oct 2016 08:23:49 GMT by s_ac15 (squid/3.5.20)
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 use event viewer error 7001 to record events. The service exposes functions that allow programs to maintain and manage
Event Viewer Error Codes List
the event logs and perform operations on the logs, such as archiving and clearing. As such, administrators can maintain event event viewer error 36888 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 is quite possible http://answers.microsoft.com/en-us/windows/forum/windows_vista-windows_programs/unable-to-start-event-viewerevent-log-service-on/2c2eae52-67c0-425d-a154-ede59d6c9eaf 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 it helps. Sometimes http://www.thewindowsclub.com/windows-event-log-service-not-starting 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 and ensure that its value is set at
Start 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 site About Us Learn more about Stack Overflow the http://serverfault.com/questions/280415/windows-event-log-service-wont-start-how-to-figure-out-cause company Business Learn more about hiring developers or posting ads with us Server Fault Questions Tags Users Badges Unanswered Ask Question _ Server Fault is a question and answer site for system and network administrators. Join http://www.sevenforums.com/performance-maintenance/183795-event-log-does-not-start.html them; it only takes a minute: Sign up Here's how it works: Anybody can ask a question Anybody can answer The best answers are voted up and rise to the top Windows Event Log service won't start event viewer - how to figure out cause up vote 4 down vote favorite Windows Event Log service will not start, it says "Error 2: The system cannot find the file specified." I've tried sfc /scannow and it reported zero issues. All other services start up fine, so svchost.exe isn't the issue. I'm guessing there is some permission or path issue or missing file, but I don't what I should do to find out where it event viewer error is failing. Is process explorer useful in this situation? If so, what do I watch for? EDIT After watching what failed using Process Monitor, the "fix" for my particular situation was to create a registry key at HKLM\System\CurrentControlSet\services\eventlog\Parameters\ServiceDll containing the same value as the key HKLM\System\CurrentControlSet\services\eventlog\ServiceDll I'm a big fan of mysterious windows self-reconfigurations. windows-7 windows-service share|improve this question edited Jun 14 '11 at 21:57 asked Jun 14 '11 at 19:03 jayrdub 218512 3 Have you checked the logs? Oh wait.... –mfinni Jun 14 '11 at 19:47 Thanks for updating with specific information. Saved me loads of annoyances. –Rob Stevenson-Leggett Mar 1 '12 at 8:22 add a comment| 2 Answers 2 active oldest votes up vote 5 down vote accepted Process Monitor would be more useful than Process Explorer. You would filter on only the executable that is used by the service. I don't have a Win7 box in front of me, so I can't check what that is. Run it, try to start the service, and see what fails. share|improve this answer answered Jun 14 '11 at 19:49 mfinni 31.2k33474 2 Thanks for the tip on process monitor, I was able to see that it was looking for a registry key that doesn't exist and created the key with the value it was looki