Setup application known issues

You cannot install a standby BlackBerry® Enterprise Server on a computer that already hosts a BlackBerry Administration Service. (DT 1123791)

Workaround: Uninstall the BlackBerry Administration Service before installing a standby BlackBerry Enterprise Server with BlackBerry Administration Service.

The setup application overwrites the MSI installation log file when you rerun it. (DT 1102412)

Workaround: Before rerunning the setup application, copy the MSI installation file.

The setup application indicates that services started successfully even though they might not have. (DT 1073106)

If you install the BlackBerry® Enterprise Server in Italian, the advertisements include some Spanish. (DT 1065265)

If you change the User name and Organization information when reinstalling or upgrading the BlackBerry Enterprise Server, the setup application does not record the change. (DT 1040901)

Workaround: After the setup application closes, manually edit the following registry settings:

  • for a 32-bit version of Windows®: HKEY_LOCAL_MACHINE\SOFTWARE\Research In Motion\BlackBerry Enterprise Server\OwnerInformation
  • for a 64-bit version of Windows: HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Research In Motion\BlackBerry Enterprise Server\OwnerInformation

If you rerun a setup application, it will mistakenly show the BlackBerry Collaboration Service as installed if the following events occurred during the upgrade process:

  • you select Microsoft® Lync™ Server 2010
  • you click Next
  • you go back to the Setup Options page to unselect the BlackBerry Collaboration Service
  • you complete the upgrade process without the BlackBerry Collaboration Service (DT 1039504)

You cannot reinstall the BlackBerry Enterprise Server with the BlackBerry Administration Service on the same computer using the same BlackBerry Configuration Database. (DT 1030904)

Workaround:
  1. Navigate to C:\Windows\System32\drivers\etc.
  2. Open the hosts file in a text editor.
  3. Create a new entry pointing to the IP address and the BlackBerry Administration Service pool name (for example, 123.123.2.1 newpoolname.domain.com).
  4. Save and close the file.
  5. At a command prompt, type ipconfig /flushdns to flush the local DNS cache.
  6. Restart the installation process. During the installation process, use the new BlackBerry Administration Service pool name.
  7. After the installation process completes, in the BlackBerry Configuration Panel, in the Administration Service - High Availability tab, change the pool name to the original pool name.
  8. Click Synchronize.
  9. Click OK.
  10. Update the hosts file to use the original pool name.
  11. Restart the BlackBerry Administration Service.

If you install a standby BlackBerry Enterprise Server with BlackBerry MDS Connection Service, map the BlackBerry MDS Connection Service to the primary BlackBerry Administration Service, and then run the setup application again on the standby BlackBerry Enterprise Server, the BlackBerry MDS Connection Service is remapped to the standby BlackBerry Enterprise Server. (DT 1024145)

Workaround: Use the BlackBerry Administration Service to remap the BlackBerry MDS Connection Service.

During the BlackBerry Enterprise Server 5.0 SP3 installation process, the text in the dialog box that prompts you to shut down services is incomplete in the German language. (DT 1015289)

If you install BlackBerry Enterprise Server 5.0 SP3 and you want to view the BlackBerry Configuration Panel, it might take a few minutes to open. (DT 1012449)

If you install the BlackBerry Administration Service on a computer that you already installed JRE™ 1.6.18 on, the BlackBerry Enterprise Server 5.0 SP3 installation process displays the "Error to writing to a database" error message when you click on "Start services" and you cannot start the BlackBerry Administration Service. (DT 1006683)

If you install BlackBerry Enterprise Server 5.0 SP3 and then you install the BlackBerry Attachment Service on a different computer in the BlackBerry Domain, the remote BlackBerry Attachment Service is missing the BlackBerry Controller instance and logging instance in the BlackBerry Administration Service. (DT 998837)

When you install the BlackBerry Enterprise Server software, if you set the DebugLogLevel registry key in HKEY_LOCAL_MACHINE\Software\Research In Motion\BlackBerry Enterprise Server\Setup\ to six, the installation process changes the value of the DebugLogLevel registry key to four and the installation process does not produce the expected level of detail in the log files. (DT 992506)

The installation process might appear to stop responding for approximately one minute when installing a BlackBerry Router in the DMZ. Do not cancel the installation process; the process is working as designed. (DT 990609)

When installing the BlackBerry Enterprise Server, when you are entering the SRP and BlackBerry® Client Access License information, if you do not click the Verify button before clicking OK, you will be prompted to verify you have entered the correct SRP and CAL information. (DT 959420)

When installing the BlackBerry Enterprise Server in German, some buttons in the user interface appear in English. For example, when completing a step, the buttons Yes and No will be in English. (DT 946825)

If you installed or upgraded the BlackBerry Enterprise Server to version 5.0 SP2 or later, upgraded JDK® and JRE, and then upgrade the BlackBerry Enterprise Server, the setup application reinstalls the versions of JDK and JRE that existed on your system just after you installed BlackBerry Enterprise Server 5.0 SP2 or later. (DT 769397)

If the BlackBerry Enterprise Server uses an evaluation license key and you upgraded using an in-place upgrade process, the BlackBerry Administration Service does not permit you to log in. (DT 743460)

When you install a remote BlackBerry Monitoring Service, by default, the setup application selects the BlackBerry® Web Desktop Manager for installation as well. (DT 703612)

If you install BlackBerry Administration Service in a BlackBerry Domain that includes an earlier version of BlackBerry Administration Service running on another computer, the setup application stops the services for the BlackBerry Administration Service, but does not automatically select BlackBerry Administration Service. This can leave your organization without a running BlackBerry Administration Service. (DT 636597)

Workaround: Select BlackBerry Administration Service manually.

You cannot remove the BlackBerry Administration Service when you run the setup application a second time. (DT 630701)

CE events are not formatted correctly in the Windows® Event Viewer. (DT 630448)

Workaround:
  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.

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)

Workaround: In the BlackBerry Administration Service, connect the BlackBerry Collaboration Service to the BlackBerry Enterprise Server.

If the BlackBerry Domain includes a primary BlackBerry Enterprise Server that is not part of a 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 run the setup application for a second time and the setup application cannot connect to the BlackBerry Configuration Database, the setup application displays the "Error initializing system" error message and does not permit you to change the BlackBerry Configuration Database information. (DT 601826)

Workaround:
  1. Click Start > Run.
  2. Type regedit.
  3. Perform one of the following actions:
    • If you are running a 32-bit version of Windows, navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Research In Motion\BlackBerry Enterprise Server.
    • If you are running a 64-bit version of Windows, navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Research In Motion\BlackBerry Enterprise Server.
  4. Remove the Database key.
  5. Perform one of the following actions:
    • If you are running a 32-bit version of Windows, navigate to HKEY_CURRENT_USER\SOFTWARE\Research In Motion\BlackBerry Enterprise Server.
    • If you are running a 64-bit version of Windows, navigate to HKEY_CURRENT_USER\SOFTWARE\Wow6432Node\Research In Motion\BlackBerry Enterprise Server.
  6. Remove the Database key.
  7. Restart the setup application.

If you use Japanese characters when specifying the name of the BlackBerry Enterprise Server, after the installation process completes, the BlackBerry Messaging Agent cannot initialize users and the BlackBerry Controller log file and the Windows Event Viewer include the "AnalyzeEntry: Bad entry received" error message. (DT 580230)

If the setup application cannot create the BlackBerry Monitoring Service database because you do not configure database permissions, the setup application stops responding. (DT 579856)

Workaround: Configure database permissions and try again.

In BlackBerry Enterprise Server 5.0 SP2 or SP3, you can find the BBSRPTool in C:\Program Files\Research In Motion\BlackBerry Enterprise Server. (DT 534090)

When you install a standby BlackBerry Enterprise Server, if you select BlackBerry Administration Service in the Setup options dialog box, you cannot cancel the selection. (DT 525015)

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)

You cannot run a BlackBerry Enterprise Server pair with different instant messaging servers configured for the primary and standby, but the setup application allows you to install the BlackBerry Enterprise Server instances with different instant messaging servers. (DT 426882, SDR 280876)

The setup application does not display an error message if there is a mismatch between ports selected by the Microsoft® SQL Server® and BlackBerry Enterprise Server in the following scenario:
  • You install the Microsoft SQL Server with a static port and the SQL Browser running.
  • You indicate that the Microsoft SQL Server is using a dynamic port during the BlackBerry Enterprise Server installation.
  • You stop the SQL Browser. (DT 391897)

The setup application does not provide a notification that the Terminal Service Application mode is installed and that you cannot install the BlackBerry Enterprise Server. (DT 364214)

On certain dialog boxes in the setup application (for example, the Administration Settings dialog box), the setup application highlights Back as the default button rather than Next. (DT 330239)

When the setup application tries to install Microsoft SQL Server 2005 Express Edition on a computer that hosts an MSDE that includes an MSDE instance named "BlackBerry", the setup application stops responding. (DT 315437)

During the installation process, if you choose to install the BlackBerry Enterprise Server in a non-default location, the setup application cannot create the key store for the BlackBerry MDS Integration Service. (DT 313541)

Workaround:
  1. Close the setup application.
  2. Create the C:\Program Files\Research In Motion\BlackBerry Enterprise Server\MDS\webserver path.
  3. Restart the setup application.

In certain circumstances, if you have previously installed the BlackBerry Enterprise Server on a computer without enabling Use Active Directory authentication on the Setup options page, and then run the setup application and enable Use Active Directory authentication, the setup application does not check whether it can communicate with global catalog servers. (DT 307428)

If you install a standalone BlackBerry Router and do not connect to the BlackBerry Configuration Database, the setup application displays an empty Console addresses dialog box. (DT 263430)

In the setup application, in the Database options screen, the name for the Use a Microsoft® SQL Server® database option should be Use an existing Microsoft SQL Server to host my database. (DT 233462)

The default for the DebugLogMaxDailyFileAge logging registry key in HKEY_LOCAL_Machine\Software\Research In Motion\Blackberry Enterprise Server\Logging Info is 14 and therefore the BlackBerry Mail Store Service logs are automatically deleted after 14 days. This does not match the default of 0 for the other logging registry keys. (DT 231153)

Workaround: You can manually update the setting in the registry to 0.

When you install the BlackBerry Enterprise Server on a 64-bit operating system, if you specify a new location for the installation folder, the setup application prompts you to confirm the creation of the folder and then reverts to the default installation folder. (DT 218745, DT 890684)

Workaround: Specify the new location of the installation folder again.

The BlackBerry Collaboration Service does not start after you change the database for a BlackBerry Enterprise Server. (DT 126765)

Next topic: SNMP known issues
Previous topic: Security known issues

Was this information helpful? Send us your comments.