Message flow entries in the BlackBerry Enterprise Server debug log

28 Jan 2012

Support Center » Knowledgebase » Message flow entries in the BlackBerry Enterprise Server debug log

	Message flow entries in the BlackBerry Enterprise Server debug log

Solution Summary
This article applies to the following:

BlackBerry Enterprise Server®
Microsoft® Exchange

--------------------------------------------------------------------------------

Details
The table below shows the BlackBerry Enterprise Server message flow as displayed in the debug log:

Line

Debug Log Entry

Description

1
[40423] (02/25 01:10:00): {Test.User@Testing.env} Queuing new mail through notification (external). EntryId=1001
The Microsoft Exchange Server notifies the BlackBerry Enterprise Server that there is a new email message in the user accounts mailbox.

2
[40465] (02/25 01:10:00): {Test.User@Testing.env} Get source key for this MAPI object, EntryId=1001
The BlackBerry Enterprise Server retrieves the source key for the new message.

3
[40435] (02/25 01:10:00): {Test.User@Testing.env} Queuing new mail through notification. EntryId=1001. Msgs Pending 0
The BlackBerry Enterprise Server queues the message for compression.

4
[30085] (02/25 01:10:00): {Test.User@Testing.env} New mail has arrived, EntryId=1001
The message is compressed.

5
[40287] (02/25 01:10:00): {Test.User@Testing.env} Queuing message, RefId=-2002, EntryId=1001
The message is placed in the outbound queue.

6
[30066] (02/25 01:10:00): Total Msgs Pending 1
The BlackBerry Enterprise Server places a flag in the user accounts mailbox. The flag is used to increase the pending messages count statistic to the BlackBerry® wireless device.

7
[40140] (02/25 01:10:00): Encrypting using key ID 0A602A71E+G+1
The BlackBerry Enterprise Server encrypts the message.

8
[30081] (02/25 01:10:00): {Test.User@Testing.env} Sending message to device, size=1023, EntryId=1001, RefId=-2002, TransactionId=-1109657118, Tag=333
The BlackBerry Enterprise Server sends the message to the BlackBerry infrastructure.

9
[40279] (02/25 01:10:00): {Test.User@Testing.env} SubmitToRelaySendQ, Tag=333
The message is received by the BlackBerry infrastructure successfully.

10
[40000] (02/25 01:10:00): [SRP] Send data, Tag=333
The message has been sent to the BlackBerry infrastructure.

11
[40000] (02/25 01:10:16): [SRP] Received status DELIVERED, Tag=333
The BlackBerry infrastructure reports back to the BlackBerry Enterprise Server that the message was sent successfully to the device. The BlackBerry Enterprise Server then increases the number of messages forwarded to the device statistic.

12
[30096] (02/25 01:10:16): Total Msgs forwarded to Handhelds 121
The debug log displays the total number of messages forwarded to the device.

13
[30097] (02/25 01:10:16): {Test.User@Testing.env} Message has been delivered to device, Tag=333, EntryId=1001
The BlackBerry Enterprise Server acknowledges that the message was sent successfully to the device, and decreases the pending messages count to the device statistic.

Follow the flow of a single message.

Determine the time a message arrived in the mailbox (line1).
Record the EntryId of the message, for example, EntryId=1001.
Use the EntryId to follow the message flow to find the Tag reference. For example, the EntryId appears in line 8 with Tag=333.
Follow the message flow using Tag=333 to line 13.
Use the logged message flow to determine possible problems:

If a long time frame exists between lines 1 and 5 in the message flow process, investigate the possibility of an issue with the BlackBerry Enterprise Server.
If a large time frame exists between lines 10 and 11 in the message flow process

Article Details

Article ID:

103

Created On:

11 Apr 2007 10:54 AM