I am having the exact same problem with Windows 2000 Advanced Server. I first noticed it today, and I also noticed from the system log that a Windows automatic update (KB824105) was applied recently. Do you think there is any possibility that the update has something to do with the application log problem? My application log shows there should be 1,857 events, but the log is blank. Actually, the lines are all there and they are selectable, but the lines are blank and double-clicking on them does nothing. I tried to save the application log and the resulting text file was empty, and in the process the event viewer console crashed. I get the same effect when logging on with different administrative usernames, and also when viewing the server's log from a remote workstation. Note that all the other logs (security, system, directory service, DNS, file replication, IExplore) are working normally. Any help you can offer is greatly appreciated.

0

Additional info: After I click on "Application Log" and the events don't appear, if I click on any of the other logs, they no longer show up anymore. I have to then close the Event Viewer and open it again to look at the other logs.

0

I have looked on the Internet trying to find a solution, and I can't find one either. These are still only guesses, but maybe trying one of these might help. 1. Check the permissions on the .evt files themselves (the files that event are logged in). See if somehow the permission got changed, and maybe that's why you can't view the events. 2. Do a virus scan with the latest definitions if you have not done so already. Maybe there is a virus that is interferring with the event viewing in an attempt to hide itself. 3. Try right clicking on the individual Events and "Clear All Events". Maybe this will rebuild the .evt files and start properly logging events. 4. The .evt files may be corrupt beyond repair and need to be deleted so that they can be recreated. The following URL is Microsoft's directions on how to delete .evt files. Use at your own risk. http://support.microsoft.com/?kbid=172156 A lot of maybes, yes, but hopefully one of them may solve your problem.

0

Save your Application log (or any other log) and then clear it out. Close Event Viewer and then reopen. Logs will show up "Except" log that was cleared out. You can reopen that log from the file you saved.

0

I had the same problem as Dale and Rajeev and i tried clearing the log. That worked and the new logs are ok. Still the saved old one's remain invisible when reloaded to event viewer. But you can read them with a text editor (not very comfortable)

0

I have the same problem as Dale has on his server. I did all of the following with no result: 1. I've checked the permissions on the application log file. "C:\Winnt\system32\config\AppEvent.Evt". The rights were set up correct. ("Full control" for the account "system" and the global group "Administrators") 2. I've run a virusscan with the latest virus definitions. 3. I've cleared the application log. 4. I've set the properties for the application log at "Overwrite events as needed". Dane and Rajeev, if you have been able to solve the issue, could you post the solution? And if someone else has any idea what I could try next, except reïnstall the server, it will mean a lot to me. Regards, Arend

0

The last point from the "Analyst" I hadn't tried yet: --------------- 4. The .evt files may be corrupt beyond repair and need to be deleted so that they can be recreated. The following URL is Microsoft's directions on how to delete .evt files. Use at your own risk. http://support.microsoft.com/?kbid=172156 --------------- My Application log was indeed corrupt although I didn't recieved the message: --------------- The handle is invalid Dr. Watson Services.exe Exception: Access Violation (0xc0000005), Address: 0x76e073d4 --------------- This would be the message I should get when a log is corrupt. Well, whatever, at least the eventviewer is working properly again.

0

Anyone else still having this problem? I have the same problem on three Windows 2000 server machines. I reinstalled the OS on two of them and it started happening again. I noticed this after installing service pack 4. I tried clearing all the logs and it works for a while but then it starts happening again. I think I am going to call Microsoft tech support about this.

0

I've been having the exact same problem since installing Service Pack 4 & other critical updates on all servers. The application log appears to be blank. If I click on application log first, then security & system logs are also blank.

0

The problem has seemed to stop after clearing all event logs. It would not work by just clearing the application log.

0

I had the same problem, all I did to fix this problem is save the log that had an error, and cleared out the event logs for app, security, etc. The log that has an error is a lost cause, but to prevent this from happening again, I increase the size of the event log to be created to some large number. I think the default was 512kb but I increased so haven't got the same error now, it seems, when the log hits its maximum size it errors out. To increase the size of the file you go to go to your event viewer, and select the log u want to increase (appl, security, system) and than go to properties and in there is a event log size, just increase it to what ever u see fit.

0