Setup application known issues
(DT 393021) After you install or upgrade to BlackBerry® Enterprise Server 4.1 SP7, the BlackBerry MDS Connection Service might not start because the MSVCR71.dll file might not be installed in the proper location on the computer.
Workaround: Copy the MSVCR71.dll file from <drive>:\Program Files\Research In Motion\BlackBerry Enterprise Server\MDSS\jre\bin to <drive>:\Program Files\Research In Motion\BlackBerry Enterprise Server\MDS\bin.
(DT 327711) If you modify the remote database connection information during the installation process (after the reboot) and then you try to create the BlackBerry Configuration Database and click Back to return to the database information screen, the Microsoft® SQL Server® name is greyed out and the BLACKBERRY instance name is added to the remote Microsoft SQL Server name.
Workaround: Use the default installation path in the setup application, or before installing the BlackBerry Enterprise Server, create the path C:\Program Files\Research In Motion\BlackBerry Enterprise Server\MDS\webserver\ to contain the BlackBerry MDS key store file.
(SDR 370652) If you run the setup application to remove a BlackBerry Attachment Service, BlackBerry Dispatcher, or BlackBerry MDS Connection Service that has stopped running, the setup application cannot remove the service. You must restart the computer and run the setup application again to complete the removal and install the service again.
(SDR 234488) The setup application might not complete successfully due to language scripts in the errors.sql file.
(SDR 192765) If you configure your BlackBerry Enterprise Server to use "Triple DES only" or "AES only", and you run the change database wizard to associate the BlackBerry Enterprise Server with an existing BlackBerry Configuration Database, the encryption algorithm for the BlackBerry Enterprise Server changes to "Triple DES and AES".
Workaround: Change the Windows machine name to use upper case before you perform the upgrade, or edit the MDSConfig table in the BlackBerry Configuration Database to use the correct instance number and remove the additional entries that reference the same machine name.
Workaround: Create a temporary registry key named Components in HKEY_LOCAL_MACHINE\Software\Wow6432Node\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18. Delete this registry key after the installation process completes successfully.