
1. Click Start > Run.
2. Type regedit.
3. Navigate to HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\EventLog\Application.
4. Change the value of BESCryptoKernel to the correct path for the CE.dll file.
5. Restart the BlackBerry Enterprise Server.
When installing the BlackBerry Administration Service, the setup application might stop responding and the value of the "JVM®
Option Number 8" registry key is blank if the computer does not have sufficient disk space for the setup application to extra
the temporary installation files. (DT 622976)
Workaround: Add the registry key manually.
1. Click Start > Run.
2. Type regedit.
3. Navigate to \\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\BAS-AS\Parameters.
4. Change the value of JVM Option Number 8 to -
Djboss.partition.name=RIM_BES_BAS_HA_########_BLACKBERRYNEW.
5. Restart the BlackBerry Administration Service.
If the computer does not have sufficient disk space, the setup application might stop responding. You might encounter this
issue if the setup application needs to install the JRE™ but there is not enough disk space for the setup application to extract
the JRE installation files. (DT 622355)
If you configure a BlackBerry Enterprise Server to connect to a remote BlackBerry Collaboration Service, and then install a
BlackBerry Collaboration Service with the BlackBerry Enterprise Server, the local BlackBerry Collaboration Service cannot start.
(DT 617662)
After you upgrade remote components from version 5.0 SP1 to version 5.0 SP2, the BlackBerry Administration Service displays
incorrect version information for BlackBerry Controller instances installed with remote components. (DT 617030)
If the BlackBerry Domain includes a primary BlackBerry Enterprise Server that is not part of an high availability pair, if you
remove a BlackBerry Administration Service and run the setup application again, you cannot install a standby BlackBerry
Enterprise Server. (DT 615520)
When you upgrade the BlackBerry Enterprise Server from 4.1 SP7 to 5.0 SP2, the setup application prompts you for the SRP
ID and SRP authentication key. (DT 614767)
Workaround: Type the SRP information and continue with the upgrade process. Duplicate errors might appear in the log file.
Release Notes
Setup application known issues
55
Kommentare zu diesen Handbüchern