![]() Using the same technique that I described above for the Application log, investigate these categories, remember the key menu is Filter source: MSExchangeSA – Active Directory related.Click on the View Menu, Filter and select one of these from the Event Source box. My reply is: ‘ master Event Viewer’s Filter ‘. ![]() People often say ‘finding the problem is like looking for a needle in a haystack’. Therefore in the case of Exchange 2010, I urge you to begin with the Application Log. Whenever I get an email problem, I try and make myself look in the Event Viewer earlier, rather than later in the troubleshooting process. Unfortunately there is no central location to view all these Exchange related logs, therefore you have to start exploring locations such as the \exchsrvr folder, Event Viewer and even the root of the C:\ or D:\ drive. If that is not enough, you can create your own performance logs. On an Exchange server there are database logs for the mailstore, Windows 2008 application logs, SMTP protocol logs and virus logs. ![]() The reason that Exchange 2010 has so many logs in so many locations is simply because it has so many components. However, I have always felt that from the earliest Windows operating systems Microsoft provides lots of troubleshooting information in their logs.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |