
If you used the "Specify new device password and lock device" IT administration command, or the "Delete all
device data and disable device" IT administration command, the audit records for the BlackBerry Enterprise Server
did not indicate which user account you used the IT administration command on. (DT 625187)
In previous releases of the BlackBerry Enterprise Server, if you tried to move multiple user accounts to a different
BlackBerry Enterprise Server, the BlackBerry Administration Service was not able to move the user accounts with
pending deployment jobs. In BlackBerry Enterprise Server 5.0 SP3, when you try to move multiple user accounts
to a different BlackBerry Enterprise Server, you are prompted to choose whether you want to move only the user
accounts with no pending deployment jobs or if you want to stop any pending deployment jobs and move all of
the user accounts. (DT 620767)
If a user account's address book location was recorded incorrectly in the BlackBerry Configuration Database, you
might not have been able to view the settings for the user account in the Organizer data synchronization tab in
the BlackBerry Administration Service. A "request could not be completed" error was displayed and an
IndexOutOfBounds error was written in the BlackBerry Attachment Service log file. (DT 619414)
In certain circumstances, the BlackBerry Administration Service repeatedly wrote the following error message to
its log file: "Violation of PRIMARY KEY constraint 'PK_BASJobTaskDependencies'. Cannot insert duplicate key in
object 'dbo.BASJobTaskDependencies." (DT 617678)
If your BlackBerry Domain included a BlackBerry Enterprise Server 4.1 SP6 and a BlackBerry Enterprise Server 5.0
SP1 or later, and you added a user account to the BlackBerry Enterprise Server 4.1 SP6, you could not change the
synchronization mappings for the user's organizer data. (DT 616603)
If you configured a BlackBerry Administration Service pool and you restarted multiple BlackBerry Administration
Service instances at a time, the BlackBerry Administration Service instances might not have identified a singleton
and errors might have occurred. (DT 613238)
The BlackBerry Administration Service now performs additional sanitization of log output to ensure sensitive
information is not recorded. (DT 610321)
In certain circumstances, if you pushed a software configuration out to a large number of users (for example,
2000), the BlackBerry Administration Service used more than its maximum of 670 threads and stopped
unexpectedly with an out of memory error. (DT 608647)
When you accessed the BlackBerry Administration Service and the BlackBerry Monitoring Service in two different
tabs in the same Windows® Internet Explorer® window, the BlackBerry Administration Service timed out. (DT
605059)
The BlackBerry Administration Service did not support searching for user accounts using the mailbox ID. As a result,
if you used the BlackBerry Enterprise Server User Administration Tool, you could not search for user accounts by
canonical name. (DT 604566)
Release Notes
BlackBerry Administration Service fixed issues
11
Kommentare zu diesen Handbüchern