Event ID 20394 occurs for users in the Event Viewer for Applications

Article ID: KB19478

Type: Support Content

Last Modified: 03-01-2012


Product(s) Affected:

  • BES5
  • BlackBerry® Enterprise Server 4.1 to 5.0 SP3 for Microsoft® Exchange
  • BlackBerry® Enterprise Server 4.1 to 4.1 SP6 for Novell® GroupWise®

Even though the BlackBerry® smartphone user is not enabled for PURGED_MESSAGE_LIST processing, the BlackBerry smartphone sends a PURGED_MESSAGE_LIST command to the BlackBerry® Enterprise Server.

Event Source: BlackBerry Messaging Agent BES01 Agent 1
Event Category: None
Event ID: 20394
Date: 9/6/2009
Time: 06:12:24 PM
User: N/A
Computer: BES01
The description for Event ID ( 20394 ) in Source ( BlackBerry Messaging Agent BES01 Agent 1 ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: {test.user@domain.com} Received PURGED_MESSAGE_LIST from device for user not enabled for purged message list processing.

The BlackBerry Enterprise Server will disregard the PURGED_MESSAGE_LIST command because the BlackBerry smartphone user on the BlackBerry Enterprise Server is not enabled for this command. 

Confirm the following lines from the Agent Log for the same time as the event:

[40700] (09/06 09:12:24.009):{0x17A4} {test.user@domain.com} Receiving packet from device, size=2563, TransactionId=965089578, Tag=4493776, content type=CMIME, cmd=0x3
[40698] (09/06 09:12:24.009):{0x17A4} {test.user@domain.com} Receiving OTAFM request from device, Tag=4493776, TransactionId=965089578
[30219] (09/06 09:12:24.009):{0x17A4} {test.user@domain.com} Received PURGED_MESSAGE_LIST from device, Tag=4493776, TransactionId=965089578
[20394] (09/06 09:12:24.009):{0x17A4} {test.user@domain.com} Received PURGED_MESSAGE_LIST from device for user not enabled for purged message list processing
[30197] (09/06 09:12:24.009):{0x17A4} {test.user@domain.com} Sending OTAFM_CONFIG to device, ServerSupport=207, UserConfig=63, Conflict=1
[40583] (09/06 09:12:24.009):{0x17A4} {test.user@domain.com} Sending packet to device, Size=48, Tag=4199669, TransactionId=-895354957
[40279] (09/06 09:12:24.009):{0x17A4} {test.user@domain.com} SubmitToRelaySendQ, Tag=4199669
[40699] (09/06 09:12:24.009):{0x17A4} {test.user@domain.com} OTAFM request from device processed
[40279] (09/06 09:12:24.009):{0x17A4} {test.user@domain.com} SubmitToRelaySendQ, Tag=4493776

This is normal behavior and this event can be disregarded.  See  additional information section for an alternate issue that can occur.

CollapseAdditional Information

If the log section from the Agent Log contains the following log line, the BlackBerry smartphone user may encounter an issue with folder redirection being disabled.

[40864] (05/31 18:02:42.949):{0x16B0} {test.user@domain.com} Received MODIFY_FOLDER from device, Tag=43818, TransactionId=269933713

See KB18549 for more information about this issue.


By downloading, accessing or otherwise using the Knowledge Base documents you agree:

   (a) that the terms of use for the documents found at www.blackberry.com/legal/knowledgebase apply to your use or reference to these documents; and

   (b) not to copy, distribute, disclose or reproduce, in full or in part any of the documents without the express written consent of RIM.

Visit the BlackBerry Technical Solution Center at www.blackberry.com/btsc.