Logging known issues
The BlackBerry® Enterprise Server does not log the long term Entry ID for notifications. (DT 1178187)
The BlackBerry Messaging Agent logs RESCAN_ST_CHANGES messages instead of RELOAD_FOLDERS messages in its log file for busy worker threads. (DT 1156492)
If you activate a BlackBerry device with the Middle East language pack on BlackBerry Enterprise Server 5.0 SP2 or later, change the input language on the device to Arabic, and turn on logging for BlackBerry® Messenger using an IT policy rule in the BlackBerry Administration Service (set the Disable BlackBerry Messenger Wireless Synchronization IT policy rule from the PIM Synchronization policy group to No), when you send a message in Arabic to another device using BlackBerry Messenger, the log displays the Arabic characters as question marks in the message. (DT 1014073)
When the BlackBerry Enterprise Server crashes, the BlackBerry Messaging Agent writes an empty stack trace to its log file. (DT 771491)
If you specify a deletion date for static agent logs in the MAGT log, the search criteria used to remove old log files only searches for log files with an instance number of two digits but the static agent IDs have an instance number of three digits. Therefore the search is not successful and the static agent logs are not deleted. (DT 606891)
The setting that you configure for Debug Log Maximum Daily File Age in the BlackBerry Administration Service does not affect static agent logs in the MAGT log. You must manually delete the static agent logs in the MAGT log. (DT 606849)
If you trigger a stack trace for the BlackBerry Messaging Agent on a 64-bit Windows Server® using a 32-bit application, the stack information does not include the threading context. (DT 597288)
In BlackBerry Enterprise Server 4.1 SP7 and 5.0 SP1 log files, the warning "Ensure that IPv6 is disabled on the Microsoft® Exchange Server or configure the BlackBerry Enterprise Server to use the closest global catalog server" is misleading. (DT 514844)
In rare circumstances, the BlackBerry Enterprise Server logs show that BlackBerry devices are out of coverage when the devices are in coverage. (DT 468720)
The location of each user’s Tasks should be listed as each user’s mail file in the BlackBerry Messaging Agent log file, but instead the location is blank in the BlackBerry Messaging Agent log file. (DT 401077, SDR 301360)