Event Viewer Error 4201
Contents |
be down. Please try the request again. Your cache administrator is webmaster. Generated Sat, 15 Oct 2016 08:16:46 GMT by s_ac15 (squid/3.5.20)
Name Passed Was Not Recognized One of our readers faced a problem where the Windows Event Log failed to start, and as a result, a couple of other error 4201 the instance name passed was not recognized services failed as well. Attempting to start the Windows Event
Error 4201 Outlook
Log service manually via the Services MMC resulted in error 4201. The complete error message is error 4201 the instance name passed windows server 2008 r2 provided below:Windows could not start the Windows Event Log service on Local Computer.Error 4201: The instance name passed was not recognized as valid by a WMI data http://answers.microsoft.com/en-us/windows/forum/windows_7-performance/cannot-start-windows-event-log-service-on-windows/e2c218ad-8637-49ee-8023-50eae0e4ddcb provider.And the following errors popped up when opening the Event Viewer and Task Scheduler.Event Log service is unavailable. Verify that the service is running.Task Scheduler service is not available. Task Scheduler will attempt to reconnect to it.Upon checking the Event Log service registry key and values, they were intact. Eventually the problem turned http://www.winhelponline.com/blog/fix-event-log-error-4201-instance-name-not-recognized/ out to be the incorrect permissions for the C:\Windows\System32\LogFiles\WMI\RtBackup directory. The SYSTEM group needs full control permissions for the directory only then the Windows Event Log service would start. Thanks to Alexzhu for sharing the solution here. Note that we didn't have to rename or delete the RtBackup directory.Fixing the Permissions for RtBackup Folder in Windows 7 and Windows Vista1. Start Windows in Safe mode2. Open the "C:\Windows\System32\LogFiles\WMI" folder3. Right-click on the RtBackup folder and choose Properties4. Click the Security tab, and click the Edit button. 5. Click Add6. Type SYSTEM and hit ENTER7. Enable "Full control" Permission to "Allow"8. Click OK, and then click Yes when asked for confirmation.9. Restart Windows (in Normal mode), and verify if the Windows Event Service has started.Unable to assign permissions for the RtBackup folder?If you're unable to assign permissions for the RtBackup folder, try taking ownership of the folder, and then repeat the steps 1-9 above.Share this article on: FacebookTwitt
number of problems which are directly linked to the WMI provider. People have said that they have experienced the following error message: Error 4201: The instance name passed was not recognized http://www.personalcomputerfixes.com/general-errors/how-to-fix-error-4201-on-windows/ as valid by a WMI data provider. What Causes The Error 4201 Normally http://helpdesk.maytechgroup.com/support/solutions/articles/135860-windows-event-log-service-fail-to-start these kinds of errors are caused because of the program that it relates to and so below are the main causes of the following error: Specific Windows files and settings are damaged or corrupt Registry keys cannot be found Files have been removed How To Fix The 4201 Error Step 1 - Rename The error 4201 WMI Folder The "WMI" folder is basically what Windows uses to help load up a number of important pieces of software & data for your system. If you are experiencing the 4201 error, it generally means that the references to this folder are damaged and should be changed. Here's how to do this: Use msconfig to switch to safe mode boot Boot to safe mode Run cmd.exe as event log service an administrator Type "cd C:\Windows\System32\LogFiles\WMI" Type "rename RtBackup RtBackup2" Use msconfig to switch to normal boot mode Reboot and find event viewer working Step 2 - Clean Out The Registry Download This Registry Cleaner One of the big causes of the 4201 errors is through the “registry” database of your computer. This is a large database which stores vital information & settings for your PC, and is used continually to help Windows to read the files, settings & options that it needs to run. Although the registry is one of the most important parts of every Windows system, it’s continually causing a large number of problems thanks to the way it will often become corrupted and unreadable. This is the cause behind many 4201 errors, and needs to be resolved by using a reliable “registry cleaner” application. This step is best completed by downloading RegAce System Suite, and letting it clean out any of the problems that your system may have inside. » Download Windows Repair Tool Highly Recommended This is our recommended cleaning tool that works to fix 99% of all the errors and issues on your PC. You can use this cleaner to stop viruses, errors and faults with your
20 Oct, 2014 at 12:51 PM while trying to troubleshoot printing issues on a machine, the event logs weren't available. Trying to start them gave a "service error 4201 the instance name passed was not recognized as valid by a WMI data provider". I found the following articles helpful in resolving the problem - basically granting the SYSTEM account full control to the %systemroot%\system32\LogFiles\WMI\RtBackup folder. A couple of months ago, one of the techs tried changing the permissions on the C: drive to fix a problem - I believe that caused this problem. http://www.winhelponline.com/blog/fix-event-log-error-4201-instance-name-not-recognized/ http://social.msdn.microsoft.com/Forums/windowsdesktop/en-US/c75ae899-d05b-411d-a7f2-00fdd33b8589/event-log-error-4201-errorwmiinstancenotfound http://social.technet.microsoft.com/Forums/windows/en-US/95987ca3-a1b2-4da6-95b7-d825d06cdac7/error-code-4201-the-instance-name-passed-was-not-recognized-as-valid-by-a-wmi-data-provider Did you find it helpful? Yes NoSend feedback Sorry we couldn't be helpful. Help us improve this article with your feedback. Related Articles Home Solutions Cookie policy We use cookies to try and give you a better experience in Freshdesk. You can learn more about what kind of cookies we use, why, and how from our Privacy Policy. If you hate cookies, or are just on a diet, you can disable them altogether too. Just note that the Freshdesk service is pretty big on some cookies (we love the choco-chip ones), and some portions of Freshdesk may not work properly if you disable cookies. We’ll also assume you agree to the way we use cookies and are ok with it as described in our Privacy Policy, unless you choose to disable them altogether through your browser.