We help IT Professionals succeed at work.

Error reading event log

Last Modified: 2013-11-29
I have a realy strange error on one of our servers.

When I open the event viewer and try to open one of the eventlogs (application, system...) the MMC freeze up and the OS totally loose control of that session with MMC. I'm able to start another MMC and perform whatever I want except looking at eventlogs.

When I try to log off the server it is not able to log me off, and if  I try to log on locally or connect to the server on RDP it's not possible. To be able to logon I have to disconnect the power or hold the powerbutton pressed until the server is turned off.

And now to the situation which to me makes this really peculiar...

If I open the log files from another server (event viewer/connect to another computer) I'm able to open the logs without any problem. If I have opened the logs remotly BEFORE I open them locally I have no problem at all! I can open the event logs, log off/on open the eventlogs and everything looks great. I'm also able to log off and log on again and still able to open the eventlogs.

Any suggestions?
Watch Question

Felix LevenSenior System and Databaseadministrator

My first try would be:

!I have done this two or three times on 2003 Servers (*.evt) and have not tryed it out on 2008+ Servers with XML eventlogs yet!

1. Disable the Startup of Eventlog Service -> Set to Startup Disabled
2. Restart Server
3. Rename or move the corrupt *.evtx files from the following location: %SystemRoot%\System32\Config
4. re-enable the EventLog service by setting it back to the default of Automatic startup
a_ro_noTechnical Account Manager

I would suggest checking the resources on that particular server e.g available Memory, Disk.
There are also some hotfixes that could help.


Btw, when you check the logs remotely are there any relevant event entries?
Distinguished Expert 2019

Try to run the system file checker with your server 2008 r2 setup dvd first.

   sfc /scannow

Yeah, event logs do occasionally get corrupted.  I've had similar situations where I could view the first screen full of entries, but after I paged through a few more, I'd get a lockup (or an error message).  In those cases, I just copied the corrupted log file to a safe place, and then just emptied the log file to fix the problem.
This one is on us!
(Get your first solution completely free - no credit card required)


The eventlog tok a "self-repair"...

Gain unlimited access to on-demand training courses with an Experts Exchange subscription.

Get Access
Why Experts Exchange?

Experts Exchange always has the answer, or at the least points me in the correct direction! It is like having another employee that is extremely experienced.

Jim Murphy
Programmer at Smart IT Solutions

When asked, what has been your best career decision?

Deciding to stick with EE.

Mohamed Asif
Technical Department Head

Being involved with EE helped me to grow personally and professionally.

Carl Webster
CTP, Sr Infrastructure Consultant
Empower Your Career
Did You Know?

We've partnered with two important charities to provide clean water and computer science education to those who need it most. READ MORE

Ask ANY Question

Connect with Certified Experts to gain insight and support on specific technology challenges including:

  • Troubleshooting
  • Research
  • Professional Opinions
Unlock the solution to this question.
Join our community and discover your potential

Experts Exchange is the only place where you can interact directly with leading experts in the technology field. Become a member today and access the collective knowledge of thousands of technology experts.

*This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.


Please enter a first name

Please enter a last name

8+ characters (letters, numbers, and a symbol)

By clicking, you agree to the Terms of Use and Privacy Policy.