BlackBerry Administration Service fixed issues
If one BlackBerry® Administration Service instance sent a reconciliation task to a second instance, and the connection between the instances dropped so that the reconciliation task failed, reconciliation stopped on all BlackBerry Administration Service instances. The first BlackBerry Administration Service instance then wrote the following error to its log file: “org.jboss.remoting.CannotConnectException: Can not get connection to server. Problem establishing socket connection for InvokerLocator [sslsocket:”. The BlackBerry Administration Service checks for unprocessed reconciliation events every 24 hours and restarts them at that time. For more information, contact RIM Support. (DT 1159175)
The BlackBerry Administration Service did not stop trying to send invalid notifications, which generated large log files, caused performance issues, and prevented administrators from logging in. (DT 993127)
In an environment that included a large number of users and applications, the BlackBerry Administration Service reconciled tasks slower than expected. (DT 980881)
If the BlackBerry Administration Service generated and queued a large number of tasks and the BlackBerry Administration Service instance that started processing the tasks stopped, the processing took longer than expected until the instance started again. (DT 968146)
In earlier releases of BlackBerry Enterprise Server Express, for optimal performance, you could only install 4 BlackBerry Administration Service instances in a pool. (DT 900359)
An issue existed in the BlackBerry Administration Service whereby proxy access configurations were not appropriately encoded when stored in the database. (DT 894703)
If you applied the Disallow Third Party Application Downloads IT policy rule to a BlackBerry device, the BlackBerry Administration Service created a job task to remove existing third-party and RIM add-on applications associated with software configurations from the device. (DT 890899)
If the BlackBerry Administration Service had a large number of jobs to process after the 5 minute timeout elapsed, the BlackBerry Administration Service might not have processed all of the jobs. (DT 887734)
When you upgraded the BlackBerry® Enterprise Server Express software, the BlackBerry Administration Service deleted application control policies that did not have an English locale name. (DT 863816)
When you moved a user from one BlackBerry Enterprise Server Express to another within a BlackBerry Domain, the BlackBerry Administration Service would needlessly push applications that were previously pushed wirelessly to the user's device before the user was moved. (DT 857857)
In some circumstances when you issued a "Delete all device data and disable device" command to a user's device and then the user activated a new device before the original device acknowledged thecommand, the BlackBerry Administration Service disabled the user's new device after an hour. (DT 836520)
For a BlackBerry Enterprise Server Express that was installed on Windows Server® 2008 R2, if you installed the Microsoft security update for KB 979683 (MS10-021), you could not use the BlackBerry Administration Service. (DT 786855)
When you configured integrated Microsoft® Active Directory® authentication, and the LDAP password was 32 characters or more, you could not access or configure the BlackBerry MDS Connection Service in the BlackBerry Administration Service. (DT 773809)
If there were many Kerberos™ services in the environment, you might not have been able to log in to the BlackBerry Administration Service using Windows® authentication due to a request timeout. (DT 711491)
Due to an incorrect value in the BlackBerry Configuration Database, you might not have been able to delete users and the BlackBerry Administration Service log file included the following error message: " [org.hibernate.util.JDBCExceptionReporter] [ERROR] Violation of UNIQUE KEY constraint 'IX_HandheldConfig_Name'. Cannot insert duplicate key in object 'dbo.HandheldConfig'" (DT 716329)
If you installed a new BlackBerry Enterprise Server Express instance and you imported the BlackBerry® Client Access License keys into the new BlackBerry Configuration Database using a database script instead of using the BlackBerry Administration Service or the setup application, administrative users might not have been able to log in to the new BlackBerry Administration Service. BlackBerry Enterprise Server Express 5.0 SP3 includes an auto-correction feature that allows you to import BlackBerry CAL keys into a BlackBerry Configuration Database directly using a database script. (DT 708890)
The BlackBerry Administration Service now prevents administrators from making changes beyond their intended permissions. (DT 704203)
If you set the Disposition application control policy rule to Required, pushed an application to a device, and then pushed an upgrade of the application to the device, the device could not install the application. The BlackBerry Administration Service displayed the "Device Reported a general failure installing the module" error message. (DT 690469, DT 643197)
If you installed a new BlackBerry Administration Service instance and selected an existing BlackBerry Configuration Database during the installation process, and the carrier name that was stored in the BlackBerry Configuration Database was long, the BlackBerry Administration Service did not permit you to manage shared drives or BlackBerry Device Software update bundles. (DT 689474)
On the Instance information tab for a BlackBerry Attachment Service instance, the General section listed Document cache size (MB) instead of the correct label, Document cache size (number of documents). (DT 654416)
When you applied multiple IT policies to a user account and your organization included many users and groups, the reconciliation process might have taken longer than was expected and the BlackBerry Administration Service might have stopped responding. (DT 639176)
In certain circumstances, the clock on the computer that hosted the BlackBerry Administration Service ran slowly. (DT 633701)
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 Express did not indicate which user account you used the IT administration command on. (DT 625187)
In previous releases of the BlackBerry Enterprise Server Express, if you tried to move multiple user accounts to a different BlackBerry Enterprise Server Express, the BlackBerry Administration Service was not able to move the user accounts with pending deployment jobs. In BlackBerry Enterprise Server Express 5.0 SP3, when you try to move multiple user accounts to a different BlackBerry Enterprise Server Express, 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)
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)
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)
The BlackBerry Administration Service did not parse the .alx file in an application bundle correctly if the .alx file referenced the same directory more than once, and on separate lines. (DT 579943)
If you assigned a software configuration to a user account and then tried to view the user's configuration information in the BlackBerry Administration Service, you might have been logged out of the BlackBerry Administration Service. (DT 571423)
When you configured the distribution settings for an IT policy to run every day at specific times (for example, 3:00 PM), and configured the default delay to be greater than the difference between the next distribution time and the current time (for example, the default delay was 15 minutes and the current time was 2:50 PM), the distribution job did not run until the next day. (DT 559148)
If you used the BlackBerry Administration Service to create an email message signature for a user account, the signature might have appeared slightly different in the user's email messages (for example, the signature might have included a extra blank line in the email message). (DT 545641)
In the BlackBerry Administration Service, if you viewed the status of reconciliation events and refreshed the page in your web browser, the BlackBerry Administration Service might have generated a system error. (DT 535218)
If you sent a Set Owner Information command over the wireless network to a device, the event was not logged by the BlackBerry Administration Service. (DT 528724)
The From and Sent To fields were limited to 150 characters in the BlackBerry Administration Service when creating message filters. (DT 526699)
An issue in the BlackBerry Administration Service could have resulted in security feature misuse due to lack of secure credential handling. (DT 526157)
Multiple issues in the BlackBerry Administration Service could have resulted in potential Cross Site Scripting (XSS) and Cross Site Request forgery vulnerabilities. These issues are resolved by improved validation of URLs. (DT 525829)
In some circumstances, you could not push applications that relied on the vendor ID over the wireless network using the BlackBerry Enterprise Server Express. The BlackBerry Administration Service resolved only a hexadecimal value for the vendor ID. (DT 522454)
The BlackBerry Administration Service displayed an exception error if the body of a custom activation message began with a plus (+) sign. (DT 520133)
If you had set the BlackBerry Device Software deployment managed by BlackBerry Administration Service option to Yes, when you upgraded the BlackBerry Enterprise Server Express, the current settings in the Default IT Policy returned to the original default settings. (DT 508621)
When you exported summary data for a large number of user accounts using the BlackBerry Administration Service, the transaction time limit might have been exceeded, which prevented the action from completing successfully. (DT 508049)
The EJB3 remote connection functionality that is part of JBoss® Web Server now correctly applies specified cipher restrictions. (DT 507404)
The BlackBerry Administration Service could not manage user accounts that were duplicated in the BlackBerry Configuration Database. (DT 501446)
If you accessed the BlackBerry Administration Service in a language other than English using Mozilla® Firefox® or Safari, the information in the Status section on the home page of the BlackBerry Administration Service appeared in English. (DT 495829)
When you sent a "Delete all device data and disable device" IT administration command to certain devices, the BlackBerry Administration Service closed. (DT 482771)
The description for the Enterprise Administrator role in the BlackBerry Administration Service stated that the enterprise administrator had all rights as a security administrator, except that the enterprise administrator could only view role assignments. (DT 482257)
The BlackBerry Administration Service cached administration permissions, allowing for stale permission application. (DT 479462)
If the Allow user wireline activation field was set to No on the BlackBerry Web Desktop Manager Information tab in the BlackBerry Administration Service, you could not activate a device using the BlackBerry Administration Service. (DT 461923)
The audit scripts for the BlackBerry Administration Service did not log when a group was created or the group name changed. (DT 444932)
An issue in the BlackBerry Administration Service where anonymous ciphers were supported could have led to weak or no access control on communications channels. Support for anonymous ciphers has been removed from the BlackBerry Administration Service configuration. (DT 410053)
When using multiple tabs in Windows Internet Explorer 7 to access the BlackBerry Administration Service, the information you typed in one tab might have appeared in another tab. (DT 387664)
You could not send PIN or email messages from the BlackBerry Administration Service without populating both the Message subject and Message body fields. (DT 266040)