Début

BlackBerry Enterprise Server Log, BB device and Outlook Communication

BlackBerry / technology

Tags: , , , , , , , ,

January 28, 2009 9

In this first part of the five-part series, I will walk you through the BES Log  and various user activities on both Outlook and BB device that will affect the way BES to log its entries from my own observation. Bear in mind this is not official but it is documented due to lack of information available on the web with regards to BES logging. Hopefully it will help you in troubleshooting.

Part I – Sending email from BlackBerry (BB) device and from Outlook
Part II – Receiving email and notification to BB device
Part III – Email Status change (read, unread etc.)
Part IV – Deletion from BB device and from Outlook
Part V – Mark Prior Opened from within BB device

The most useful log or the one that you probably end up using is something look like this: SERVERNAME_MAGT_01_20090123_0001.txt In addition to the log entries found below, you can also click on the screen capture of the log for better viewing.

Sending e-mail from Outlook

=== SERVERNAME_MAGT_01_20090123_0001.txt ===

  1. [40423] (01/23 12:21:10.712):{0×1AC0} {cat@cheelam.com} Queuing new mail through notification (external). EntryId=279873
  2. [40435] (01/23 12:21:10.712):{0×1F34} {cat@cheelam.com} Queuing new mail through notification. EntryId=279873. Msgs Pending 0
  3. [30233] (01/23 12:21:10.744):{0×1F34} {cat@cheelam.com} New message was found in SentItems, EntryId=279873
  4. [40287] (01/23 12:21:10.869):{0×1F34} {cat@cheelam.com} Queuing message, RefId=-219078018, EntryId=279873, Posted=01/23 12:21:08, Delivered=01/23 12:21:08
  5. [30066] (01/23 12:21:10.869):{0×1F34} Total Msgs Pending 1
  6. [40671] (01/23 12:21:10.947):{0×1B38} {cat@cheelam.com} Not sending message body (5 bytes), RefId=-219078018, EntryId=279873 [30081] (01/23 12:21:10.947):{0×1B38} {cat@cheelam.com} Sending message to device, size=175, EntryId=279873, RefId=-219078018, TransactionId=-914755543, Tag=581159
  7. [40279] (01/23 12:21:10.947):{0×1B38} {cat@cheelam.com} SubmitToRelaySendQ, Tag=581159
  8. [40000] (01/23 12:21:10.947):{0×1B08} [BIPP] Send data, Tag=581159
  9. [40000] (01/23 12:21:13.900):{0×1B04} [BIPP] Received status DELIVERED, Tag=581159
  10. [30097] (01/23 12:21:13.900):{0×1B3C} {cat@cheelam.com} Message has been delivered to device, Tag=581159, EntryId=279873
  11. [30066] (01/23 12:21:13.962):{0×1B3C} Total Msgs Pending 0

When I click send in Outlook, it took less than 3 seconds to notify my BlackBerry Curve. As you can see there are 10 transactions being carried by BES from detecting, queuing, sending, getting confirmation back from device and updating its status in BlackBerry Enterprise Manager. All these took 1 sec. The rest of the delay are user action and communication with mailbox, cellular infrastructure, and Exchange-Outlook update. Still, this is very impressive.

image
Click to enlarge
Emailing from Outlook

Sending from BB device

=== SERVERNAME_MAGT_01_20090123_0001.txt ===

  1. [40700] (01/23 12:46:07.391):{0×1F38} {cat@cheelam.com} Receiving packet from device, size=124, TransactionId=573264607, Tag=280023, content type=CMIME, cmd=0×3
  2. [30112] (01/23 12:46:07.391):{0×1F38} {cat@cheelam.com} Receiving message from device, RefId=1935722939, Tag=280023, TransactionId=573264607
  3. [40292] (01/23 12:46:07.548):{0×1F38} {cat@cheelam.com} Email message sent for device, Tag=280023
  4. [40279] (01/23 12:46:07.548):{0×1F38} {cat@cheelam.com} SubmitToRelaySendQ, Tag=280023
  5. [40000] (01/23 12:46:07.548):{0×1B08} [BIPP] Send status DATA_ACCEPTED, Tag=280023

When sending email from my BB Curve, it took only 5 transactions instead of 10 like the one from Outlook. And for about 10 seconds, that email got updated in my Outlook’s Sent folder. The transaction is very much self-explanatory. Pay attention to RefId and Tag. I will cover that more later in the my next post .

image
Click to enlarge
Sending from BlackBerry Device

Coming up Next Part II – Receiving email and notification to BB device

This website uses IntenseDebate comments, but they are not currently loaded because either your browser doesn't support JavaScript, or they didn't load fast enough.

9 Comments

    [...] Originally Posted by besadmin44 Hi I am looking for all info possible on BES Logs, what I should look for, what they are good for and how to use them. Also, daily best practices for BES running Domino. thanks Check this out: BlackBerry Enterprise Server Log, BB device and Outlook Communication | D

  • [...] fourth of my five part series in BlackBerry Enterprise Server debug log articles. This time let’s take a look at deletion operation from both Outlook as well as BB device and [...]

  • [...] concluded my five part series of BlackBerry Enterprise Server Debug log communication with Outlook and BB device. Hopefully you will find this case study and observation will aid you in troubleshooting directly [...]

  • [...] concluded my five part series of BlackBerry Enterprise Server Debug log communication with Outlook and BB device. Hopefully you will find this case study and observation will aid you in troubleshooting directly [...]

  • [...] BlackBery Enterprise Server Log communication with BB device and Outlook. The first part was about Sending email from BlackBerry (BB) device and from Outlook. If you notice, there are two sets of logs I captured in my first article. From a sender stand [...]

    • Kyle
    • Mar 31, 2009, 23:08
    • Reply

    Great blog on Bes logs, reveals the mystery some what. Do you have any log information for when a device get’s activated? I have a issue with a couple of people with new devices, the MAGT is logging the message scan, and the etp file is getting delivered to the Exchange mailbox. But I get the following:

    ignored – let other server/desktop do it, EntryId=90943
    and
    Still handled by desktop

    From what I read, the device has been provisioned from the carrier as a device capable of desktop redirection only or BIS capable only. Is there a way to force the device to receive the required service books, from the carrier, for BES capabilities with out having to call the carrier support?

    Thanks for putting together a great blog.

    Cheers

    • Hi Kyle, somewhat… I don’t have the activation log. From carrier, you can log in to BIS webpage for that particular device (register it if not) and you will have the option to resend service book from the RIM/carrier page. One thing you have to distinguish is, at least in Canada, BIS and BES are different data plan. A user can have BIS (without BES capability) or have BES (with both BIS and BES). So if you want to force BES capability, you as the administrator of your company have to go to Blackberry Enterprise Manager console to do it. The carrier page management interface is only for BIS. Chee

    • andy
    • Aug 31, 2009, 4:06
    • Reply

    great Blog,
    did i miss the bit about a retention policy for the logs? is 90 days standard practice?
    i hardly ever go into my logs at all but they have blown out to over 15gb. i inherited it from the previous administrator and it has logs set to keep indefinitely (setting of "0" in "debug log maximum file age")

  • Andy, great question. Those are default setting. Most company would want to keep for record and periodically archive them in order to maintain the drive space. Unfortunately this is part of our job to ensure it does not over blown your drive. Chee

Leave a Reply