BlackBerry Monitoring Service known issues
After a BlackBerry® Enterprise Server pair fails over, the BlackBerry Monitoring Service stops updating user counters for the BlackBerry Synchronization Service. (DT 1138760)
Workaround: Restart BlackBerry Monitoring Service.
If the BlackBerry® Monitoring Service database includes tables with NULL values, the BlackBerry Threshold Analysis Tool cannot run. (DT 1103114)
If you set the Regional and Language settings on the computer to German (Austria), the BlackBerry Threshold Analysis Tool cannot run. (DT 1094072)
The BlackBerry Monitoring Service adds duplicate entries to the BlackBerry Monitoring Service database until the size limit is reached, which can cause the BlackBerry Monitoring Service to stop responding. (DT 1040956)
If you uncheck the Create daily log folder option in the BlackBerry Configuration Panel, the BlackBerry Monitoring Service writes each log line in a separate file. (DT 1032103)
If a threshold is triggered before or during a failover event, the alarms are not removed from the alarm panel after the failover event. (DT 1019154)
Workaround: Restart the BlackBerry Monitoring Service.
Alarms are not removed from the alarm panel after a user threshold is passed. (DT 1016300)
Workaround: Restart the BlackBerry Monitoring Service.
In the BlackBerry Monitoring Service, when you view the Messages pending field for several BlackBerry Messaging Agent instances, the field displays the same number of messages pending for all instances. (DT 1012768)
You cannot complete the diagnostic test using the BlackBerry device dashboard on a device that is running BlackBerry® 6. (DT 990885)
In an environment that includes multiple instances of the BlackBerry Messaging Agent, in certain circumstances the SNMP service does not report the correct hung thread count, so the hung thread count that the BlackBerry Monitoring Service displays is not accurate. (DT 972469)
If you add an email address or PIN address to the BlackBerry Monitoring Service notifications list while the SNMP service is not available, when you check Notifications > Manage addresses in the BlackBerry Monitoring Service console, the email address or PIN address displays ( ). (DT 905668)
When you use the BlackBerry Monitoring Service in a Latin-based language and test the configuration settings for servers that the BlackBerry Monitoring Service uses SNMP to monitor, the BlackBerry Monitoring Service displays an exception error. (DT 887617)
In the BlackBerry Monitoring Service, when you create a custom BlackBerry Attachment Service report in a Latin-based language and add report columns, the names of the report columns change to English, the report column field clears, and the generate report request fails. (DT 887607, DT 887596)
In the BlackBerry Monitoring Service, when you create a custom report in a Latin-based language, all of the report types in the Select report type drop-down list appear in English except for BlackBerry Attachment Service. Also, if you click a report type other than Attachment Type and then click the Select report type drop-down list, Attachment Type appears in English. (DT 887593)
If you change the name of the BlackBerry Administration Service pool, the BlackBerry Monitoring Service does not display the new name. (DT 753182)
Workaround: Reinstall the BlackBerry Monitoring Service.
If email addresses include special characters, when you try to create a contact using that email address, the BlackBerry Monitoring Service displays a system error and logs you out. The BlackBerry Monitoring Service Polling Engine service also stops. (DT 632907)
The BlackBerry device dashboard displays all timestamps in UTC time, not in the timezone that the device uses. (DT 629272)
After the BlackBerry Enterprise Server fails over, when you access the BlackBerry Monitoring Service console, you do not see the login page and cannot log in. The BlackBerry Monitoring Service writes the following error message to its log file: "com.rim.bes.bas.web.common.CommonExceptionPresenter] [WARN] [BBAS-2007] {unknown} Caught unknown exception" (DT 626752)
Workaround: Restart the BlackBerry Monitoring Service.
You cannot remove preconfigured threshold rules. If you try to delete them, they are automatically recreated. (DT 619039)
Workaround: Disable the rule instead.
When you try to turn off monitoring for a non-SNMP server, the BlackBerry Monitoring Service can display the "Request not completed" error message, even though it does turn off monitoring. This issue is intermittent. (DT 614951)
If you press the F5 key or click the Refresh button to refresh the BlackBerry Monitoring Service, the BlackBerry Monitoring Service writes an error message to its log file and logs you out. This issue applies to all pages except the home page. (DT 600023)
A .pdf file created from a quick report does not display Japanese user names correctly if the BlackBerry Monitoring Service console is in English when you create the .pdf file. (DT 596673)
When the list of messages for a monitored BlackBerry Dispatcher exceeds one page, the BlackBerry Monitoring Service displays the first page as a blank page. (DT 566030)
When you restart the BlackBerry Monitoring Service, a dialog box displays with the message "WMI Performance Adapter Service encountered a problem and needed to close". This is caused by an internal error. (DT 542948)
The BlackBerry Monitoring Service and the BlackBerry MDS Connection Service both use port number 8443 when the BlackBerry MDS Connection Service is configured to permit push applications to open trusted and untrusted connections. (DT 531776)
Workaround: Change one of the services to use another port number.
When you use a Safari browser, in the User details page, some tabs are truncated and do not display correctly. (DT 509761)
When generating a report, the BlackBerry Monitoring Service might miss events and not perform as expected. For example, if the BlackBerry Enterprise Server services stop while the BlackBerry Monitoring Service is generating a report for 1800 users, this issue might occur. (DT 491944)
When you add a thresholds rule (for example, a pending messages rule) to 2000 user accounts at one time, the BlackBerry Monitoring Service console no longer responds as expected and the application server for the BlackBerry Monitoring Service increases its CPU usage. (DT 455310)
If you delete a threshold for a user account or component data item that is in an alarm state, the alarm clears but a pass notification is not sent. As a result, an incorrect Fail message displays for a data item that is no longer in a failed state. (DT 440939, SDR 280608)
When you perform a ping test from the BlackBerry Monitoring Service console for a BlackBerry device that is connected to the BlackBerry Enterprise Server using a Wi-Fi® connection, the ping test fails. (DT 440928, SDR 291862)
If you turn off support for 8.3 file paths on the computer (by setting the HKLM\SYSTEM\CurrentControlSet\Control\FileSystem\NtfsDisable8dot3NameCreation registry key to 1), when you install the BlackBerry Monitoring Service, the web.keystore is not created. (DT 394681)
- Configure the computer to support 8.3 file paths.
- At a command prompt, run the following command: "C:\Program Files\Research In Motion\BlackBerry Enterprise Server\Monitoring Service\bin\webGenKey.bat" C:\PROGRA~1\Java\jdk1.6.0_15 C:\PROGRA~1\Research In Motion\BlackBerry Enterprise Server\Monitoring Service\besbms <FQDN_BMS_computer>.
In certain circumstances, SMS notification messages are not sent to users’ BlackBerry devices due to a large number of error messages written in the BlackBerry Monitoring Service log file. (DT 339753)
After you configure a user time-based threshold, the BlackBerry Monitoring Service writes error messages to the BBMS-DCS log file. (DT 317931)
In certain circumstances, an HTTP 500 error message is displayed when you try to log in to the BlackBerry Monitoring Service. (DT 315939)
Workaround: Remove the bas-config.properties file from the root directory.
When a user logs in to the BlackBerry device dashboard and the BlackBerry device is in a different time zone from the BlackBerry Monitoring Service, the start and end date of the certificate do not match and the user cannot connect to the BlackBerry Monitoring Service. (DT 132363)
In certain circumstances, a time-based component threshold triggers immediately after you set the threshold. (SDR 298777)