Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I ran into a weird problem on a Windows XP system. My local service app logs its diagnostic messages into the Windows Event Log, so at some point those messages stopped being logged. I thought that the issue was in my code, but then I discovered that other processes can’t log messages either.
So I was wondering, is there a limit on the Windows Event Log size?
PS. I guess I need to write this specifically — I need to know/change the size from a command line or an API.
The limit and behavior depends on the log configuration. Please check in the log properties if “When maximum log size is reached” is set to “Do not overwrite events”. If so, the events will not be logged. You can set the limit there as well.
UPDATE: It turns out the question is how to check the behavior described above programmatically. Please have a look at EventLog.OverflowAction, EventLog.MaximumKilobytes, and EventLog.MinimumRetentionDays properties, that should be enough.