BES Logs ... What's in them? Part 18 of 20 (MAPICdoErrors.exe BRK Tool)

Welcome to Part 18 of the 20 part series looking at the BES logs (Part 17) ... the BRK Tool MAPICdoErrors.exe. Another tool I keep in my arsenal, that I don't find myself using all that much, but when I do comes in very handy.

Officially labeled the BlackBerry MAPI and CDO Error Monitoring Tool, MAPICdoErrors identifies common Messaging Application Programming Interface (MAPI) and Collaboration Data Object (CDO) errors and custom events. Like the Pending tool, the MAPICdoErrors only requires the MAGT log.

Syntax

First, we look at the actual syntax of the command. The required elements are the platform and users. In my example below I'm using an Exchange log (even though this is only supported with Exchange) wanting to get a report for all users with all errors. When I'm looking for a specific user I'll insert just that email address instead of using the all flag ... or even pick a specific error I'm looking for. The output like the other files comes quickly, 5 seconds for 51MB of log and 114 users.



Result

Below is the output for just testuser1@port3101.org. Had I ran the command MAPICdoErrors.exe -p E -u testuser1@port3101.org this would have been all of the output in the file; so I simply filtered out the user data for this example. The output though, much like the Pending tool is a one to one relationship with the actual log file.



Raw Data from DISP Log

Here is how it all correlates with a snip from the MAGT log ... specifically line 2 of the above data at 09:47:34.562:
____________________

[40405] (07/01 09:47:34.562):{0xC44} {testuser1@port3101.org} MAPIMailbox::IsMAPIMessageHTMLFormatted - OpenProperty(PR_RTF_COMPRESSED) (0x8004010f) failed
____________________

Again, this tool isn't all that fancy, but if you've got a specific error you're searching for and want to isolate the users experiencing a given problem, this is a great tool. Likewise, it is good for seeing any potential issue a particular user might be having.

Also, keep this link handy: List of Extended MAPI numeric result codes ... very useful for correlating the errors to what Microsoft actually classifies the error message as.

If you've got any questions about the MapiCdoErrors tool feel free to post a question / comment in response to this post, or in the forum.

Tomorrow we'll review one final tool, and arguably my favorite: MessageFlow.exe.

If you've got any feedback or ideas for what you'd like to see more on please drop me a line.

Thanks!