Users experiencing issues connecting or using Exchange messaging service via Outlook or OWA ? Here is how to sort this out on most of the cases :

· First thing to look at is the Application Log, then the System Log,.

· Second thing to look at are the performance counters to check if we have RPC latencies (as all the actions an Exchange user is doing corresponds to RPC requests being sent to the Exchange server). The methodology is the following :

o Check for RPC latencies

o Check for CPU performance issues

o Check for Memory load issues

o Check for Disk bound issues

o Check for Network issues

o Check for Active Directory related issues

o Check for Virus scanning issues

A list of the most important counters has to be built for future reference, but the thing is, if an issue is not visible in the Application or System Log, then the Performance logging analysis will point the cause of the issue on most of the time, provided you use the correct methodology as introduced above.


· Performance analysis enable to fine-tune Exchange components analysis. For example, if users are still able to connect to the Exchange server, but they encounter huge latencies, THEN performance analysis with the right counters will tell you where the issue is.

o As there are hundreds of counters on an Exchange Server : Disks, Memory, Processor Exchange components, …, it is essential to have a subset of counters to begin with the performance anlaysis. That is the easiest and more effective approach.

o Once the component causing the Exchange issue (Disk, Memory, Network, etc…) has been identified, then we can dig further in the analysis of this component by using more of this component’s counters. For example, for the Memory component, we must check the “Available MB” and “Pages/Sec” counters, and if one of these shows an issue, then we will add more Memory counters (total counters for the Memory component is 35 ! That’s why we start with only 2 counters, Available MB and Pages/Sec. The principle is the same for all other components : take 2 to 4 significant counters, then dig further)


Here is the list of Exchange 2007 counters that will help pointing out where the issue is – I will post a link to my Excel spreadsheet if you ask, I promise ! (I currently have the same for Exchange 2003 – for Exchange 2010, take the same counters as for Exchange 2007 – I am in the process of updating the Exchange 2010 spreadsheet to have a consistent/complete Excel tool) :

Part I :

Performance Exchange part I


Part II :

Performance Exchange part II


Part II :

Performance Exchange part III