Keep in touch and stay productive with Teams and Officeeven when you're working remotely. Learn More. Learn how to collaborate with Office Tech support scams are an industry-wide issue where scammers trick you into paying for unnecessary technical support services. You can help protect yourself from scammers by verifying that the contact is a Microsoft Agent or Microsoft Employee and that the phone number is an official Microsoft global customer service number.
Did this solve your problem? Yes No.
Sorry this didn't help. April 7, Keep in touch and stay productive with Teams and Officeeven when you're working remotely. Site Feedback. Tell us about your experience with our site. Cooperdale Created on December 4, Hello, I've been getting the error in the title for a couple of weeks when I try to browse the Administrative Events custom view in Event Viewer.
I checked out this thread and the related knowledge base article but the hotfix only works for Windows Vista. I am on Windows 7 Ultimate x64 and I got the message that the hotfix doesn't work for my system I downloaded the Vista x64 file. So what should I do?
I would have no problem with completely clearing the events, if this somehow fixed the custom view. This thread is locked. You can follow the question or vote as helpful, but you cannot reply to this thread. I have the same question Cooperdale Replied on December 6, In reply to Imran Chand's post on December 6, Thanks but I disabled System Restore a long time ago, I have incremental Acronis backups but the problem is older than 2 weeks.
Anyway, I've managed to fix it. Since Administrative Events is a filter which checks all the logs, I browsed through them all one by one to see if one of them was corrupted or missing. Since I don't need that log at all, I looked for it in the registry and removed it. Now the Administrative Events filter works fine once again.When checking the Audit log in Event Viewer, it may return this error message: "Event viewer cannot open the event log or custom view.
Verify that Event Log service is running or query is too long. Access is denied 5 ". The Registry path will change accordingly, but the same principles will apply to others logs.
In this article I make these two assumptions: You are an administrator. The Windows Event Viewer service is already running properly.
Once finished, you will most likely need to restart the server for the changes to take full effect. As such, it's best to do this after-hours. Attached is a screenshot of the error: Event viewer cannot open the event log or custom view. Access is denied 5. To my knowledge, can only be corrected via the registry. First thing, we need to get a group or user SID that will get the permissions required to read the logfile.
In my example I will be applying the permission to domain administrators. Open Powershell 2. Import the active directory module if appropriate for your environment : Import-module Active Directory 3.
Open Registry editor regedit. Modify the CustomSD registry entry by adding your new value to the end. Don't replace the existing values. Just add another to the end. Home How-tos.If you prefer to fix this problem yourself, go to the " Let me fix it myself " section. Then click Run in the File Download dialog box, and follow the steps in this wizard. Note This wizard may be in English only. However, the automatic fix also works for other language versions of Windows.
Note If you are not on the computer that has the problem, you can save the automatic fix to a flash drive or to a CD so that you can run it on the computer that has the problem.
Note We would appreciate your feedback. To provide feedback or to report any issues with this solution, please leave a comment on the " Fix it for me " blog or send us an email message. Skip to main content. Verify that the event log service is running or query is too long. Access is denied" when we try to open up the security logs on some of the domain controllers with the domain admin account. We didn't have the right security permissions defined for the eventlog account in the registry.
Fix this problem Microsoft Fix it Last Updated: Mar 15, Was this information helpful? Yes No. Tell us what we can do to improve the article Submit. Your feedback will help us improve the support experience.
Server Fault is a question and answer site for system and network administrators. It only takes a minute to sign up. On two separate Windows 8. Event Viewer cannot open the event log or custom view. Verify that Event Log service is running or query is too long. The request is not supported Really old question, but I believe the answer still applies under Windows The credit for this answer goes to the comment made by Olaf Hess above, but it's absolutely correct:.
Apparently the presence of this key causes all kinds of issues for the Event Log viewer, as well as Windows Update, and possibly other things, because it makes the system believe that you're running the Windows Preinstallation Environment. Sign up to join this community.
The best answers are voted up and rise to the top. Home Questions Tags Users Unanswered. Event Log service broken on Windows 8. Asked 5 years, 8 months ago. Active 1 year, 9 months ago.Una finanza nuova per le regioni
Viewed 1k times. When I open Event Viewer I get this message when viewing any log: Event Viewer cannot open the event log or custom view. The request is not supported 50 The Windows Event Log service is running. Any ideas how to repair this?
Did you manage to find a solution? I'm experiencing the same issue with Windows Ended up reinstalling. This also lead to the installation of Windows Updates no longer working error message "Windows PE is not supported".How To Set Up Windows Event Log Forwarding In Windows Server 2016
Hope this helps. Active Oldest Votes. Dmitry Brant Dmitry Brant 3 3 bronze badges. Sign up or log in Sign up using Google. Sign up using Facebook. Sign up using Email and Password.Network administrators are interested because they are responsible for monitoring and managing the Windows Servers.Charkha working
Security professionals are interested in the Event Viewer security logs to look for any suspicious activities and security violations. Help Desk is interested in troubleshooting user login issues and account lockouts. Accessing the Event Viewer logs on a local computer is not a problem, but IT staff often needs access to these logs on the remote computers servers and workstations.
You can use the Event Viewer tool to connect to Event Viewer logs on remote computers. In this article I will show you how. I will also walk you through the steps for creating a custom console so you can monitor Event Viewer logs on multiple computers from a single console.
However, the Event Viewer is designed to view logs on one computer at a time. To view event logs of multiple computers, network administrators can create a custom Microsoft Management Console MMC. MMC is a built-in tool available on all Windows computers. All rights reserved. September 10, April 14, January 6, Verify that Event Log service is running or query is too long.
Note :- Security log successfully check with local admin Login. Hi Alexander, I have installed windows Virtual machine in my computer.
Shivraj, how are you trying to access the Event Viewer of the virtual machine? Please make sure that you are logged into both computers as an administrator. I have a concern in about few months for computer names on my event viewer. If anyone could explain I would really appreciate. However, if you upgrade a computer, its name will remain the same.Boss orange kwamero slim fit
You can simply rename the computer up to 15 characters. Your email address will not be published. This blog is visited regularly by people from over countries around the world.
Here is a list of the top 10 countries with the highest number of visitors. United States 2. Great Britain 3. India 4. Canada 5. Australia 6. Germany 7. Netherlands 8.Here is a brief overview. I have mentioned these individual updates in the respective blog posts, but there has not been a comprehensive listing so far.
Some blog readers have pointed out in comments for certain Windows versions that there is a bug fix for the event viewer e. Others had asked where updates could be found. So I decided to create a separate blog post for my readers. Windows security updates released from Microsoft in June are closing numerous vulnerabilities, but also causing headache for administrators.
As soon as the updates have been installed, the Event Viewer crashes, if custom views are selected. Click to zoom. As soon as the error has occurred once, the event viewer can no longer be used.
The reason for this is that the Event viewer snap-in automatically tried to load the last custom view selected during the next start. The article explains which Windows versions and updates are affected virtually all. And I had sketched a workaround how to fix the Event Viewer at least but no custom views can be used afterward. Microsoft had confirmed the bug quite quickly and promised to fix it by July The updates to fix the relevant bug in the Event Viewer trickled in between June 18 and June 28, The following list provides an overview of the relevant updates:.Leveling a sagging ceiling
All updates are optional and are offered via Windows Update. If you want to install these updates under Windows 10, you must actively search for the updates in the update page. For a manual installation, the packages can be downloaded from the Microsoft Update Catalog via the above KB numbers.
Most updates mentioned above comes with serious side effects. Verify that event log service is running or query is too long. The security descriptor structure is invalid Patch KB is not applicable so I could not run it.N330 capacitor
Thanks for the responses. There is nothing online regarding this issue yet. Your email address will not be published. By using this form you agree with the storage and handling of your data by this website. Born's Tech and Windows World. Skip to content. Fixes for Windows event viewer bug June Posted on by guenni. This entry was posted in issueUpdateWindows and tagged fixUpdateWindows. Bookmark the permalink. EP says:. Qiana Jones says:. Leave a Reply Cancel reply Your email address will not be published.
Leave this field empty. Search for:. Proudly powered by WordPress.Log in or Sign up. You are viewing our forum as a guest. For full access please Register.
I know we have slightly different issues with event viewer, mine won't run at all. But coincidentally, while reading up on command line commands, I came across one for dealing with the event viewer, and got this return: The Windows Event Log service is starting. The Windows Event Log service could not be started.
A system error has occurred. The system cannot find message text for message number 0x in the message file for null. Does that mean anything to anyone?
Micros. If you boot the computer into Safe Mode, does Event Viewer open successfully without any errors? Evan Omo. Log in or Sign up to hide this advert. No, it does the same error. The event log app opens, but reports that the "event log service is not running ", the same as it does when not in safemode. Obviously, the event log app shows blank. I think that means it's not recording anything at all.
I do run the MRT from time to time, but it never finds any kind of infection. I did get the saliny virus once, a while back, but I cleaned that out, and haven't seen any traces of it since.
I suppose that could have done it, but it should not still be doing anything now, and everything else saliny did killed the taskman, for instance is fixed. Lets try this fix to get Event Viewer working. After the Command Prompt window opens type the following commands and press enter after typing in each one: net stop winmgmt You will be prompted to Press Y to stop the WMI Instrumentation service so please do so.
Thanks, that did it! I had a look around in that wmi folder, I noticed there were only 2 files in the original, and the new one has 6 files in it.Download pkzip
I wonder what's up with that?