I see this time and time again ... A single BES with users from 20+ Exchange servers. One Exchange server has poor performance and instantly 20% of all BES users experience message delays, and all of their mailboxes are in a constant state of RESCAN instead of messages being delivered by UDP NOTIFY.

In addition, you notice errors in the MAGT, ALRT, and then the CTRL log indicating that it has restarted a given agent a maximum amount of times within 24 hours and it will not restart:...

Welcome to Part 7 of the 20 part series looking at the BES logs. (Part 6)

Welcome to the most overwhelming log of all ... the BlackBerry Messaging Agent (MAGT) log.

Much like the SYNC log splits off data into other logs (such as CBCK), the DISP log splits off MAGT data. In fact, you'll notice no such service in the Windows Control Panel for Messaging Agents ... but if you stop the BlackBerry Dispatcher Service you'll see any BlackBerryAgent.exe processed stop. Unlike the...