
If you install a BlackBerry MDS Connection Service that supports multiple BlackBerry Enterprise Server instances,
if the computer does not have sufficient virtual memory, the BlackBerry MDS Connection Service cannot start. In
the JVM path, the -Xmx flag is set to 1024. (DT 520221)
Workaround: Change the maximum heap size from -Xmx1024M to -Xmx768M.
The setup application does not include the disk space requirements for third-party applications that it must install
with the BlackBerry Enterprise Server in the Setup options dialog box when you install a BlackBerry Enterprise
Server for the first time. (DT 493105)
Workaround: To determine the required disk space for all applications, proceed to the Accounts and Folders dialog
box.
If you install the BlackBerry Enterprise Server for the first time in a pair, the PrepopulatePIMForNotesUsers trait
is created more than once. There should only be one PrepopuatePIMForNotesUsers trait for the ServerConfigId
for each high availability pair. This has no effect on how the BlackBerry Enterprise Server works because it only
uses the first instance of the trait. (DT 480241)
Workaround: You can disregard the second instance of the PrepopuatePIMForNotesUsers trait.
When you install or upgrade a BlackBerry Enterprise Server on a 64-bit operating system, a warning message might
display in the Preinstallation Checklist dialog box about mismatched MDAC component versions. You can safely
ignore this message. (DT 475776)
If you try to uninstall a BlackBerry Enterprise Server 5.0 and then reinstall the BlackBerry Enterprise Server on the
same computer with a different BlackBerry Enterprise Server name and configure it to use the same database, an
error message appears stating that the setup application found duplicate entries for the computer names in the
BlackBerry Configuration Database and you cannot install the BlackBerry Enterprise Server. (DT 453844)
Workaround: You must use the BlackBerry Administration Service to remove the entries from the BlackBerry
Enterprise Server instances that no longer exist in your organization's environment before you can continue with
the upgrade process.
During disaster recovery, if you change the BlackBerry Configuration Database on a primary BlackBerry Enterprise
Server to a new BlackBerry Configuration Database, and then try to change the BlackBerry Configuration Database
on the standby BlackBerry Enterprise Server, the setup application cannot complete the installation of the standby
BlackBerry Enterprise Server. (DT 427076)
Workaround: Uninstall the standby BlackBerry Enterprise Server from the computer and reinstall it.
When you reinstall a BlackBerry Collaboration Service, the setup application does not detect Microsoft® Office
Communications Server 2007. (DT 426915)
Release Notes
Setup application known issues
70
Comentarios a estos manuales