
5
Release Notes
SDR 81450 In BlackBerry Enterprise Server Version 4.1 and earlier, if the BlackBerry Policy Service checked to determine if the applications
on a user’s BlackBerry device required an upgrade while the BlackBerry Configuration Database was unavailable, the BlackBerry
Policy Service could not retrieve the user’s configuration information and might have been restarted by the BlackBerry
Controller.
In BlackBerry Enterprise Server Version 4.1 SP1 and later, this issue is resolved.
SDR 79964 In BlackBerry Enterprise Server Version 4.1, if your database environment was IBM DB2® Universal Database (DB2 UDB) and
you were migrating data from a BlackBerry Configuration Database on Microsoft SQL Server into a new BlackBerry
Configuration Database on DB2 UDB, the registry keys that defined the database location for the BlackBerry Manager were not
updated.
In BlackBerry Enterprise Server Version 4.1 SP1 and later, the registry keys are updated.
SDR 78300 In BlackBerry Enterprise Server Version 4.1 and earlier, the local BlackBerry Enterprise Server time zone was not added to the
BlackBerry Messaging Agent log file when configuration settings were listed.
In BlackBerry Enterprise Server Version 4.1 SP1 and later, the time zone is added to the BlackBerry Messaging Agent log file.
SDR 67823 In BlackBerry Enterprise Server Version 4.1, if a user downloaded a Java™ Application Download (JAD) file using the BlackBerry
Browser, in some circumstances, the file size might have displayed as zero bytes. The user might not have been able to see the
JAD file size before downloading the file.
In BlackBerry Enterprise Server Version 4.1 SP1 and later, this issue is resolved.
BlackBerry Alert Service
SDR 75889 In BlackBerry Enterprise Server Version 4.1 and earlier, when you set the maximum debug log daily file age in the BlackBerry
Configuration Panel, the BlackBerry Alert Service logs might have not been removed when the log file reached the maximum
age.
In BlackBerry Enterprise Server Version 4.1 SP1 and later, this issue is resolved.
BlackBerry Configuration Database
SDR 81072 In BlackBerry Enterprise Server Version 4.1, if your database environment was Microsoft SQL Server and you attempted to install
the BlackBerry Database Notification System (DBNS) on a named instance, the installation completed successfully but the
DBNS was not operational.
In BlackBerry Enterprise Server Version 4.1 SP1 and later, this issue is resolved.
BlackBerry Configuration Panel
SDR 80097 In BlackBerry Enterprise Server Version 4.1, if you attempted to use the BlackBerry Configuration Panel to create a new
BlackBerry Configuration Database, the "Database connection lost. Please test connection again with a valid User ID and
Password to be able to access configuration settings from the database." error message appeared.
In BlackBerry Enterprise Server Version 4.1 SP1 and later, this issue is resolved.
BlackBerry Dispatcher
SDR 85863 In BlackBerry Enterprise Server Version 4.1 and earlier, the BlackBerry Dispatcher SRP thread might have stopped responding,
which could have resulted in mail flow issues.
In BlackBerry Enterprise Server Version 4.1 SP1 and later, this issue is resolved.
BlackBerry Instant Messaging for Novell GroupWise
SDR 81912 In BlackBerry Enterprise Server Version 4.1, if you were using the Novell® GroupWise® Messenger Web console to monitor
instant messaging client connections, when a user logged into the BlackBerry GroupWise instant messaging client, an unclear
string appeared in the GroupWise Messenger Web console.
In BlackBerry Enterprise Server Version 4.1 SP1 and later, this issue is resolved.
BlackBerry Instant Messaging for Microsoft Live Communications Server
SDR 80118 In BlackBerry Enterprise Server Version 4.1, if users attempted to switch conversations using the message indicator, the
“message queue overflow” message appeared.
In BlackBerry Enterprise Server Version 4.1 SP1 and later, this issue is resolved.
SDR 79630 In BlackBerry Enterprise Server Version 4.1, if your instant messaging environment was Microsoft Live Communications Server,
when a user invited multiple users to a group conversation, the first invitee appeared to join the conversation and then
immediately leave, but never received the invitation to join and could not participate. The second and subsequent invitees
received the invitation and could join the conversation successfully.
In BlackBerry Enterprise Server Version 4.1 SP1 and later, this issue is resolved.
Key issues
Komentarze do niniejszej Instrukcji