
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.
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)
SNMP known issues
If SNMP for the BlackBerry® Monitoring Service is not set up correctly, the BlackBerry MDS Connection Service
continuously writes the following error to its log file: <ERROR>:<LAYER = SCM, BMS: setConfigConfig failed
rc=-1000>. (DT 891612)
Workaround: Consider any of the following actions:
• Verify that you set up SNMP for the BlackBerry Monitoring Service correctly.
• Remove SNMP trap information from the Windows® registry and restart the SNMP service.
• If you are not using SNMP, stop the SNMP service.
Release Notes
SNMP known issues
67
Komentarze do niniejszej Instrukcji