BES 5.0 MR1 - Release Notes
This is not available for download yet, but it appears that RIM published this document yesterday (despite the 'For RIM internal use only. Not for external distribution.' note in the document header).
Fixed issues
BlackBerry Administration Service
SDR 300554
In BlackBerry Enterprise Server version 5.0, if an application push was made to approximately 30,000 users or more, the BlackBerry Configuration Database might have experienced performance issues.
In BlackBerry Enterprise Server version 5.0 MR1, this issue is resolved.
SDR 305451
In BlackBerry Enterprise Server version 5.0, in certain circumstances, a search for all user accounts might have returned the error message "The request could not be completed."
In BlackBerry Enterprise Server version 5.0 MR1, this issue is resolved.
SDR 306687
In BlackBerry Enterprise Server version 5.0, the BlackBerry Enterprise Transporter might not have been able to update the devicexml and vendorxml rows in the GlobalSettings table of the BlackBerry Configuration Database.
In BlackBerry Enterprise Server version 5.0 MR1, this issue is resolved.
SDR 308970
In BlackBerry Enterprise Server version 5.0, in certain circumstances, after searching for a user account and receiving empty search results, the “Add user from company directory” link might not have appeared.
In BlackBerry Enterprise Server version 5.0 MR1, this issue is resolved.
SDR 309559
In BlackBerry Enterprise Server version 5.0, when the BlackBerry Administration Service was configured to retrieve XML files from an external web site and could not connect to the web site, the GlobalSettings table of the BlackBerry Configuration Database was updated with invalid data and the BlackBerry Administration Service was unable to reconcile applications to BlackBerry devices until the BlackBerry Administration Service connected to the external web site and updated the GlobalSettings table with valid data.
In BlackBerry Enterprise Server version 5.0 MR1, this issue is resolved.
SDR 316602
In BlackBerry Enterprise Server version 5.0, in certain circumstances, when assigning a BlackBerry device to a user and then searching for the user, the error message "The request could not be completed" might have appeared.
In BlackBerry Enterprise Server version 5.0 MR1, this issue is resolved.
BlackBerry Attachment Service
SDR 295875
In BlackBerry Enterprise Server version 5.0, in certain circumstances, when using a previous version of the BlackBerry Attachment Service with the most recent version of the attachment viewer, pictures that should have been rendered as fills might have be rendered as multiple tiles.
In BlackBerry Enterprise Server version 5.0 MR1, this issue is resolved.
SDR 298516
In BlackBerry Enterprise Server version 5.0, in certain circumstances, when viewing a Microsoft® Excel® attachment on a BlackBerry device, times might have display incorrectly (for example, 09:60 rather than 10:00).
In BlackBerry Enterprise Server version 5.0 MR1, this issue is resolved.
SDR 306541
In BlackBerry Enterprise Server version 5.0, in certain circumstances, if the ability for BlackBerry devices to view .doc or .ppt files was turned off and then turned on, the BlackBerry devices might not have been able to receive messages.
In BlackBerry Enterprise Server version 5.0 MR1, this issue is resolved.
SDR 314287
In BlackBerry Enterprise Server 5.0, security vulnerabilities existed in the PDF distiller of the BlackBerry Attachment Service. These vulnerabilities could have allowed a malicious individual to send an email message containing a specially crafted PDF file, which when opened for viewing on a BlackBerry smartphone, could have caused memory corruption and could have possibly led to arbitrary code execution on the computer that the BlackBerry Attachment Service runs on.
In BlackBerry Enterprise Server version 5.0 MR1, this issue is resolved.
SDR 324730
In BlackBerry Enterprise Server version 4.1 SP3 or later, security vulnerabilities existed in the font rasterization engine of the BlackBerry Attachment Service. These vulnerabilities could have allowed a malicious individual to send a specially crafted file through an application, which when opened for viewing on a BlackBerry smartphone, could have caused memory corruption and could have possibly led to arbitrary code execution on the computer that the BlackBerry Attachment Service runs on.
In BlackBerry Enterprise Server version 5.0 MR1, this issue is resolved.
BlackBerry Collaboration Service
SDR 300871
In BlackBerry Enterprise Server version 4.1 SP6 or later, in certain circumstances, if a user had AOL® contacts on their contact list, the user could not log in to the BlackBerry® Client for use with Microsoft® Office Communications Server 2007.
In BlackBerry Enterprise Server version 5.0 MR1, this issue is resolved.
BlackBerry Configuration Panel
SDR 299265
In BlackBerry Enterprise Server version 5.0, if you specified the LDAP password using the BlackBerry Configuration Panel, the password was entered into the BlackBerry Configuration Database in plain text. As a result, the BlackBerry Administration Server could not read the password, and you could not log into the BlackBerry Administration Service using Windows authentication.
In BlackBerry Enterprise Server version 5.0 MR1, this issue is resolved.
BlackBerry MDS Connection Service
SDR 305905
In BlackBerry Enterprise Server version 4.3 and later, a security vulnerability existed in the File application on BlackBerry devices. This vulnerability could have allowed users to browse the local file structure of the BlackBerry MDS Connection Service, view files, and copy files to their BlackBerry devices.
In BlackBerry Enterprise Server version 5.0 MR1, this issue is resolved.
Known Issues
BlackBerry Administration Service
SDR 295428
After running the setup application for the maintenance release, the version number of the BlackBerry Administration Service does not change.
Setup Application
SDR 319193
When you run the setup application for the maintenance release on Windows Server 2008, a permissions conflict might cause the setup application to close unexpectedly.
Workaround
1. Create a shortcut for besn500mr1.msp.
2. Right-click the shortcut, and then click Properties.
3. In the Target field, type the following text:
msiexec.exe /update besn500mr1.msp_file_location
4. Click OK.
5. Right-click the shortcut, and then click Run as.
6. Select the The following user option, and specify an administrator’s login information.
7. Click OK.
__________________
BCSA (4.1, 5.0) | BCSD (4.1, 5.0)
The views expressed by me on Port3101.org are my own and do not necessarily reflect the views of my employer.
|
Linear Mode
