How to Clear Event Log in Windows Server 2003
Windows keeps a lot of logs for every important event that happens on your computer. Most of these files contain details of system actions, changes to settings, and other daily activities. But there are some logs that also log information when things aren't working as they should, which makes them useful for troubleshooting.
There are several ways to view log files in Windows, so you can Diagnose problems Such as crashes, freezes and failed operations. We'll explain the best ways to find the solutions you need.
- How to search for records through file explorer
- How to check logs in Event Viewer
- How to browse logs with SnakeTail
- How to browse logs using FullEvenLogView
- How to view logs using reliability monitoring
- Solve specific problems using logs
- You have to believe in the power of records
How to search for records through file explorer
To view all records stored on your computer, open file explorer and select the drive C: (or whatever the primary drive letter is). write * .log in the search box and press Enter. This will scan your entire hard drive for Windows logs and logs for various applications, a process that can take several minutes. You have to wait.
There will likely be thousands of results across many different folders, so it's wise to filter the list to only show the most recent records. Click the button Modify date on the File Explorer toolbar and choose Today, Yesterday, or This Week.
Double-click a plain text log file to open it in the Notepad app. Most logs contain technical data that only developers understand, but you might see a simple English indication of the error you're experiencing, such as a file missing or an incorrect value.
How to check logs in Event Viewer
lets you "Event Viewer" Built in Windows Browse the logs of all events on your PC, including when things go wrong. If an application crashes unexpectedly, the operation fails, or is displayed blue screen of death Event Viewer can help you diagnose the problem.
Run the Event Viewer by typing eventvwr.msc in the Start menu search bar and clicking on the corresponding option. Important information is stored within Windows Logs , so double-click this option in the folder tree to open its subfolders.
If the problem is with an app or service, tap Apply. If the problem is with Windows itself, such as startup or shutdown error, click System. Either option will show you a long list of records, including the dates and times the events occurred.
Look for logs marked as warning (which usually means something unexpected happened), error (something failed), or critical (something that needs urgent treatment). To avoid browsing the entire list, click on the View menu and choose Sort by -> Level To put the logs related to the problem at the top.
Alternatively, to filter records by date and severity, click Filter current record in the Actions section. Choose an option from the Logged menu, such as Last 24 Hours or Last Seven Days. Check the boxes for Error and Criticality and click Agree.
You can also click Custom Views -> Administrative Events In the folder tree to display all warnings, errors, and important events across all types of logs. This list does not include records of information about successful operations, so it is faster to browse.
To save more time, you can search for log files for a specific application or Windows feature. Click Find in the Actions menu, enter the name of the app or feature, and keep clicking Find Next to explore related logs.
Select a record to view the event details in the section below. Double-click the log to display more information in the Event Properties window. A log summary may indicate the cause of the problem, but it is likely that you will need to figure it out on your own. We'll explain how to do this in a moment.
How to browse logs with SnakeTail
Navigating the Event Viewer can be slow and complicated unless you know exactly what you're looking for. For a faster and simpler way to browse event logs, download the free app SnakeTail Extract it and run it. You do not need to install it. Just double-click the .exe file to run once the download is complete.
to download: SnakeTail For Windows 10 (Free)
Go to File -> Open event log And choose the type of registry to open, such as App or System. SnakeTail has a tabbed interface, so you can view multiple lists of records at once.
In addition to loading logs instantly, SnakeTail makes it easy to filter them. Right-click on Level (eg Error), Date, or Source, and choose Add Filter to display only relevant results. Select an event to view the details in the section below.
How to browse logs using FullEvenLogView
as it deserves FullEventLogView From NirSoft Look. This free app lists all your records in one simple interface and lets you sort the data by criteria, including event time, level, provider, and keywords.
Scroll to the bottom of the page to find download links. When the download is complete, launch the application.
How to view logs using reliability monitoring
Instead of scrolling through long lists of records, you can use Windows' built-in Reliability Monitor to visually browse important lists. This makes it much easier to determine when the error or critical event occurred and why.
The quickest way to get to the Reliability Monitor is to type Reliability into the Start menu search bar and select View Reliability History. You can browse the reliability graph by days or weeks, and click the arrows on either side to go back and forth through time.
Look for the red error intersections and the yellow warning triangles, and click one to view a summary in the box below. Reliability Monitor only highlights hardware and app issues that have affected the stability of your system, so you won't see as many events as you would in Event Viewer.
Click View Technical Details to read an explanation of the problem. You can also choose to view all problem reports (which the Reliability Monitor logs) to browse all the stability issues your computer has had recently.
Solve specific problems using logs
Although Event Viewer tells you why an error or critical event occurred on your computer, its logs do not help you solve the problem. Clicking the Event Log Online Help link in a window event properties Just to send the record to Microsoft and open Microsoft support site (On the homepage, not a related article).
Fortunately, help is at hand from an excellent website called EventID.Net. This not only explains what specific Windows events actually mean but reveals how serious (or not) they are and provides the troubleshooting tips you need.
Copy and paste the event ID number of the log from the Event Viewer (or SnakeTrail) into the search box on the EventID.Net homepage, along with the source (application or service). For example, if you've got a Blue Screen of Death (BSoD), the event ID is usually 41, but the source will vary (Kernel Power is a common mistake).
The website's search engine will display matching events, accompanied by helpful feedback from the EventID.Net community. For BSoD errors, there are many possible causes and solutions, all of which are clearly explained.
At the time of writing, the comprehensive EventID.Net database covers 11 Windows event IDs and 588 event sources, with 638 comments. The website is free to use, but some features, such as rewriting event descriptions in plain English, require a paid subscription.
If EventID.Net isn't helpful, or the record doesn't provide the ID number, your best bet is to copy and paste the event summary into Google or Microsoft community site. It is possible that someone else has encountered the same problem.
You have to believe in the power of records
When your computer starts behaving strangely, it could be Windows logs Serves as your secret weapon for troubleshooting. Knowing where to find logs, how to view them, and what to do with their information can help you quickly identify the cause of problems and hopefully fix them.
If the logs have no answer, there are plenty of other free tools To diagnose Windows problems. Some of them will need to be downloaded, while others are usefully built into the operating system.
How to Clear Event Log in Windows Server 2003
Source: https://www.dz-techs.com/en/troubleshoot-windows-event-viewer-logs