Menu
Somehow, the Application Event log count ended up to 18,446,744,073,709,551,499. This causes MMC snap-in to fail when I want to see the event using Event Viewer, giving a System.OverflowException (Value was either too large or too small for an Int64.). Any thoughts, or should I just clear the log?
283
A. 1 Configuring the Security Event Log Set the maximum size of the Security Event Log to no less than 10 MB, and set the retention method to Overwrite events as needed.
The maximum log file size can be configured between 1 megabyte (1,024 kilobytes) and 4 terabytes (4,194,240 kilobytes) in kilobyte increments. The recommended state for this setting is: Enabled: 32,768 or greater.
The Limit-EventLog cmdlet sets the maximum size of a classic event log, how long each event must be retained, and what happens when the log reaches its maximum size. You can use it to limit the event logs on local or remote computers.
Maybe it helps if you activate the option to override old eventlogs when the log is full. This should prevent you from loosing the newest log entries when reaching the limit.
To activate navigate to your eventlog and go to their settings. There you find an option to override old entries if the log is full.
86
Before clearing the Application log I first tried "Save All Events As...", but the file it produced was empty.
I then copied C:\Windows\System32\winevt\Logs\Application.evtx to my desktop and that file DID open correctly. Not great, but an acceptable work-around for my needs.
29
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
