Beat spammers with anti-spam software for Exchange
Server – GFI MailEssentials. Download FREE
trial
Introduction to Exchange Server 2003 Logs
Logs really will help you troubleshoot virtually any Exchange 2003 problem. The idea of this page is to
open your eyes to the numerous types of Exchange logs and where to find them.
Microsoft are not perfect. However, I have always felt that from Windows 3.11 onwards Microsoft provide lots of troubleshooting information by way of logs. The reason that Exchange 2003 has so many logs is that it has
so many components. There are database logs for the mailstore, Windows 2003
application logs, protocol logs e.g. SMTP, performance logs, and virus logs. Unfortunately there is not central location to view all the logs, so you have to explore the \exchsrvr folder, Event
Viewer and even the root of the C:\ or D:\ drive.
DNS Log - Check DNS for name resolution errors which could result in connectivity problems
Exchange Server 2007 is a complex topic, do you need practical hands on training? As an MCT trainer, I can thoroughly recommend
TrainSignal. In particular, I like the way
that TrainSignal cover all learning methods, instructor lead, video and of course text
material. You can either take one module, for example Exchange 2007 or go for a combination of modules.
Learn more about Microsoft Exchange Server 2007 here
When ever there is an email problem, I try and train myself to look in the Event Viewer earlier, rather than later in the troubleshooting cycle. So in the case of Exchange 2003, begin with the Application
Log. People often say 'finding the problem is like looking for a needle in a haystack'. My reply is: ' master Event Viewer's Filter '. Click on the View Menu, Filter and select one of these from the Event Source box.
Exchange even has two setup logs to help you troubleshoot install programs. These files are created in the root of the drive where the Exchange 2003 binaries are installed. For example look
in C:\ or D:\. These files give valuable reasons why setup failed. Could not extend the schema, or problems overwriting priv1.edb in the MDBDATA folder. I once used the progress log
to solve a replication problem when migrating from Exchange 5.5.
Guy Recommends:
The SolarWinds Exchange Monitor
Here is a
free tool to monitor your Exchange Server. Download and
install the utility, then inspect your mail queues, monitor the Exchange
server's memory, confirm there is enough disk space and check the CPU
utilization. This is the real deal - there is no catch. SolarWinds
provides this fully-functioning product for free, as part of their commitment to
supporting the network management community.
When you are troubleshooting Exchange 2003, collect the evidence by going first to the event logs. Explore the numerous places and types of logs that Exchange has to offer. Find out where
to turn the logs on and learn how to interpret the output data.
The
extra features you get in your eBook include: 'How to...' sections
with screen shots. Checklists to prepare your migration plan.
