- Best Practices
- Tracking Exchange Messages
- Enabling Message Tracking
- Using the Message Tracking Center
- Using Windows 2000 Event Viewer
- Conclusion
Like this article? We recommend
Like this article? We recommend
Like this article? We recommend
Using Windows 2000 Event Viewer
For review, an event is any notable incident within the Windows 2000 operating environment. Critical events will trigger an immediate onscreen notification to the administrator. However, the more run-of-the-mill events are only logged. These need not necessarily be errors, just occurrences worth recording. Windows 2000 Performance Monitor logs three main types of events:
Application log—Operational errors and events logged by programs
Security log—Logons and permission auditing
System log—Status of system services and other system operations
The logging levels set for each Exchange component determine which events are actually logged.
You can use the Event Viewer to manage and view the events logs, as well to gather information about hardware and software. It is considered a key tool used to troubleshoot and determine the server problems.
Keep in mind that Event Viewer is a general-purpose diagnostic tool. Many of the errors generated for Exchange are sometimes vague to provide a solid solution. You should use the other tools in this article to gather information before taking any troubleshooting action.
To use the Windows 2000 Event Viewer, do the following:
On the Start menu, point to Programs, point to Administration Tools, and then click Event Viewer.
From the Event Viewer console tree, click the Application Log or any other log that you want to view. A list of log events will appear.
Double-click the event that you want to view; an Event Properties page will appear.
TIP
By clicking Source, you can filter Application Log and view Exchange events.