When your Exchange Server 2003 environment experiences a performance or stability problem, you need to be able to quickly diagnose and correct the malfunction and stem the flood of user complaints. Knowing how to collect the relevant debugging data is important. As an Exchange administrator, I've learned about several tools and techniques that can benefit your troubleshooting efforts and maximize the uptime on your Exchange servers.
Logging Debugging Information
Exchange 2003 logs informational, warning, and error events to the Application event log. Therefore, your first step in troubleshooting Exchange problems is to look in the Application event log. To view the log, open Windows Event Viewer (Start, All Programs, Administrative Tools, Event Viewer).
The default diagnostics logging level for all Exchange services is None. This level logs events such as start-up and shut-down of services, status of backup events, and errors. This logging level is adequate for single-server deployments that aren't experiencing any problems, but you'll probably need to increase logging levels for complex enterprise deployments that have many servers. . . .
)
muszyngr June 29, 2005 (Article Rating: