(Also, SP6 is available for BESX 3.6) Functional Changes: Time zone mappings for time zones not supported by CDO for Microsoft Windows
To prevent meeting appointments that occur in time zones not supported by CDO for Microsoft Windows from displaying incorrectly, you must manually map unsupported time zones to CDO for Microsoft Windows time zones. (SDR 49822) Note:
This functional change applies to BlackBerry Enterprise Server 4.0 SP2 only. MAPI call tracking and statistics reporting added to BlackBerry Enterprise Server logs
The BlackBerry Enterprise Server now tracks MAPI calls to the Microsoft Exchange Server and writes MAPI statistics to the BlackBerry® Messaging Agent log. (SDR 36952) Ability to customize the interval for resending pending messages
You can configure the number of days for which the BlackBerry Enterprise Server resends messages that are not received on BlackBerry Wireless Handhelds™. Any messages that the BlackBerry Enterprise Server cannot send in that time frame expire. (SDR 55544) Ability to save BlackBerry Manager SQL authentication credentials
The Mobile Data Service browser opens a WML script that is not well-formed or does not comply with WAP-WML. The text or link related to the non-compliant script does not display in the browser. In its place, an error message that describes the WML syntax error appears. (SDR 35426, SDR 31757, SDR 31272) Fixed Issues: BlackBerry Attachment Service: SDR 50045
Previously, if a user searched an attachment on the handheld and the search results included a text string, no results were returned. SDR 48451
Previously, in certain circumstances, a request to view a Microsoft Excel attachment that contained a very large cell might have failed. The “An unknown error was encountered” message displayed on the handheld. SDR 48092
Previously, in certain circumstances, a request to view a PDF attachment on the handheld might have timed out. BlackBerry Configuration Panel: SDR 47641
Previously, in certain circumstances, if you set the Debug Log Maximum Daily file Age setting to 1 for some components in the BlackBerry Configuration Panel, and you moved the date on the BlackBerry Enterprise Server computer ahead by two days, the BlackBerry Enterprise Server saved three days of logs instead of two days. BlackBerry Manager: SDR 47903
Previously, the Mobile Data Service log level settings were missing from the Mobile Data Service Properties window in the BlackBerry Manager. SDR 47518
Previously, if you added a user to and enabled a user for push role in the Mobile Data Service Properties window, and then closed the window, when you re-opened the window to view the user, a different user name appeared. SDR 41881
Previously, when you set the Automatically refresh user list every setting on the Advanced tab of the BlackBerry Manager Properties to a value other than None, the user list was not updated to reflect the users’ current statistics. If you right-clicked a user in the user list, and then clicked Refresh, the user’s statistics did not update. BlackBerry Messaging Agent: SDR 58115
Previously, in certain circumstances, when you moved a user’s mailbox from one Microsoft Exchange Server to another, and reloaded the user in the BlackBerry Manager, the user account was not stopped correctly before being restarted. SDR 57257
Previously, in certain circumstances, if you upgraded the BlackBerry Enterprise Server, ChangeKey errors displayed in the Exchange Connector log files. BlackBerry Mobile Data Service: SDR 55844
Previously, during an SSL connection, the Mobile Data Service did not honour the handheld request to trust a certificate. As a result, it did not load images from the untrusted web site. SDR 55248
Previously, if the srpinetaddress field in the MDSConfig database table did not match the BlackBerry Enterprise Server name of the computer on which the Mobile Data Service was running, Mobile Data Service push was unavailable. SDR 50517
Previously, the Mobile Data Service HTTP authentication type was case-sensitive. The Mobile Data Service did not process a proxy server’s authentication type if it was not delivered in the expected case. SDR 48933
Previously, if an HTTP URL redirected the Mobile Data Service to an HTTPS URL, the transcoder used HTTP to fetch the resource. Setup program: SDR 49921
Previously, the registry key, HKEY_LOCAL_MACHINE\SOFTWARE\Research in Motion\BlackBerry Enterprise Server\Servers\<Servername>\SendWindowInDays, did not perform correctly when created. You could not modify the expiry time for messages that were not received on the handheld. SDR 37783
Previously, if the cdo.dll file was not installed and registered in the system32 directory, a warning message indicating that the file could not be found appeared. SDR 30915
Previously, in certain circumstances, when you upgraded the BlackBerry Enterprise Server from version 3.6 to version 4.0, and the configuration database was on a separate computer, the installation program displayed the location of the configuration database as being on the local computer. Wireless calendar synchronization: SDR 42215
Previously, when you deleted a recurring appointment series that had an exception appointment, the exception appointment was not removed from the handheld. Wireless enterprise activation: SDR 58426
Previously, in certain circumstances, if you enabled a user for wireless enterprise activation using a version 4.0 SP1 BlackBerry Manager or the BESUserAdminClient.exe tool, the handheld could not be activated wirelessly.
Note: When you view an activation password using a version 4.0 SP1 BlackBerry Manager, the password will not display even though it is set. SDR 52908
Previously, in certain circumstances, after you added a user to the BlackBerry Enterprise Server, generated and then sent an activation message, the user did not receive the activation message before the activation password expired. The handheld could not be activated wirelessly. SDR 41896
Previously, in certain circumstances, prepopulated email messages were not populated starting from the day of the wireless enterprise activation. Also, not all prepopulated email messages that displayed on a wirelessly-activated handheld were marked with a prepopulation flag. Known Issues: BlackBerry Attachment Service: SDR 56666
In certain circumstances, Acrobat version 1.3 PDF attachments that third-party applications generate might not display correctly on the handheld. SDR 51971
Attachments that contain Czech characters might not display correctly on the handheld. SDR 44322
If the registry key (located in HKLM\SYSTEM\CurrentControlSet\Services\BBAttachSer ver\Parameters\EnableLog) is not set to 5, the BlackBerry Attachment Service and Attachment Conversion logs do not generate. BlackBerry Dispatcher: SDR 51790, SDR 50933
SNMP traps for detecting SRP connections, Mobile Data Service connections to the BlackBerry Enterprise Server and the configuration database, non-responsive threads, and whether the Mobile Data Service is started or stopped, do not get logged to the SNMP service. BlackBerry Handheld Configuration Tool: SDR 55224
In certain circumstances, the BlackBerry Handheld Configuration Tool does not correctly display branch information on the configuration tab.
Workaround: Re-index the handheld software that does not display correctly on the configuration tab. SDR 54570
If you provision a handheld at the administration computer using the BlackBerry Handheld Configuration Tool and message prepopulation is configured in the BlackBerry Manager, all messages, instead of the number of messages that you configured, prepopulate on to the handheld.
Workaround: Provision handhelds wirelessly or at the user’s desktop computer using the BlackBerry Desktop Manager. SDR 52705
If you turn off TCP/IP on the configuration database or TCP/IP a port other than the default port (1433), you cannot open the Handheld Configuration Tool.
Workaround: Verify that TCP/IP is turned on. If you are using a port other than 1433, on the BlackBerry Enterprise Server, set the port number that you want to use. In HKEY_LOCAL_MACHINE\SOFTWARE\Research in Motion\BlackBerry Enterprise Server\Database\Port, add a DWORD key with a decimal value. SDR 52601
If the For fast searching, allowing Indexing Service to index this folder check box is not selected in the PackageCache folder properties on the BlackBerry Enterprise Server, third-party applications might not deliver wirelessly to handhelds successfully.
Workaround: On the computer on which the BlackBerry Enterprise Server is installed, browse to C:\Program Files\Research In Motion\BlackBerry Enterprise Server\. Right-click the PackageCache folder, and then click Properties. Click Advanced. Select the “For fast searching, allowing Indexing Service to index this folder” check box. BlackBerry Manager: SDR 57440
In certain circumstances, if you add a user, and refresh the BlackBerry Manager, the user’s creation time statistic displays incorrectly. SDR 55528
When you view users in the BlackBerry Manager on BlackBerry Enterprise Server 3.6, the user’s IT policy statistics do not display.
Workaround: Open the user’s Properties window to view the IT policy statistics. SDR 52033
When you open the BlackBerry Manager in an environment with a BlackBerry Enterprise Server 3.6 and a BlackBerry Enterprise Server 4.0 configuration database, if you do not have administrative permissions on all the Microsoft Exchange Servers that contain BlackBerry users, the BlackBerry Manager might terminate unexpectedly. SDR 50393
When you configure the BlackBerry Manager to refresh the user list automatically, and a user property window is open when an automatic refresh occurs, the BlackBerry Manager terminates unexpectedly.
Workaround: Set the refresh rate to a higher number. SDR 46334
When you add three 5-user SBE licenses to the BlackBerry Manager and apply a 5-user SBE upgrader license, the upgrader does not upgrade the licenses. The “The existing license permits a maximum of 15 users. The license key would exceed the limit and thus cannot be added to the license manager" message displays in the BlackBerry Manager. SDR 42694
If, in the BlackBerry Manager you turn off S/MIME encryption for signed and weakly encrypted messages, you must restart the BlackBerry Enterprise Server for the changes to take effect. BlackBerry Messaging Agent: SDR 56128
In certain circumstances, if the Microsoft SQL Server computer on the which the configuration database exists stops responding, the Messaging Agents might also stop responding.
Workaround: Restore operation to the Microsoft SQL Server computer and restart the BlackBerry Controller. SDR 55338
In certain circumstances, if a Domain Controller stops responding in a BlackBerry Enterprise Server environment, users might not be able to send messages from their handhelds. SDR 53494
If you restart the BlackBerry Enterprise Server, the TimerHealth thread might not start correctly for a user. The user cannot send messages from or receive messages on the handheld.
Workaround: Restart the BlackBerry Controller. SDR 50786
In certain circumstances, if a message is copied in Microsoft Outlook® to a folder that is redirected to the handheld, the message might not be delivered to the handheld. SDR 49649
In certain circumstances, the Messaging Agent does not display accurate SNMP values for besConfigSRPPort and besSYSHealthSrpConnectedState. SDR 43054
If you move a user to a different mail store on the same Microsoft Exchange Server, the user cannot send or receive messages on the handheld.
Workaround: Reload the user in the BlackBerry Manager or restart the BlackBerry Controller. BlackBerry Mobile Data Service: SDR 38731
Proxy mappings do not work until you restart the Mobile Data Service. SDR 33227
SNMP traps for the Mobile Data Service do not appear correctly in an SNMP trap viewer. BlackBerry Policy Service: SDR 44122
When you assign an IT policy that contains custom policy rules to a handheld that previously had an IT policy assigned, the IT policy is not sent to the handheld. An error is written to the BlackBerry Policy Service logs.
Workaround: Make the handheld unavailable. Delete all stored information from the handheld. Assign the custom IT policy to the user. Reactivate the handheld. Note:
Back up all handheld information before making the handheld unavailable and deleting all of the stored information. BlackBerry Router: SDR 42551
In certain circumstances, the BlackBerry Router does not start correctly after it is restarted.
Workaround: On the computer on which the BlackBerry Router is installed, at the command prompt type BlackberryRouter.exe --remove, and then type BlackberryRouter.exe --install. BlackBerry Synchronization Service: SDR 58902, SDR 58900
In certain circumstances, if the configuration database stops responding, certain configuration database errors might cause the BlackBerry Synchronization Service to incorrectly add address book entries on or remove address entries from the handheld. SDR 57470
When you add a user to the BlackBerry Manager, and then activate the user wirelessly, the initial synchronization of PIM data to the handheld does not complete successfully until you restart the Synchronization Service.
Workaround: Restart the Synchronization Service after you activate a user wirelessly. SDR 56240
If the Synchronization Service is turned off, the SRP connection to the BlackBerry Dispatcher is not stopped. Users start up incorrectly and user threads might become non-responsive when you restart the Synchronization Service.
Workaround: Restart the BlackBerry Controller. Configuration database: SDR 49638
When you enable peer-to-peer encryption on BlackBerry Enterprise Server 4.0, users on BlackBerry Enterprise Server 3.6, who are connected to the same version 4.0 configuration database, cannot send PIN messages to users on BlackBerry Enterprise Server 4.0. SDR 48851
If multiple BlackBerry Enterprise Servers connect to a single configuration database, and multiple BlackBerry Routers, the BlackBerry Enterprise Server might send incorrect BlackBerry Router information to the handheld. Setup program: SDR 54868
If you upgrade the BlackBerry Enterprise Server from version 4.0 or earlier, users cannot view Microsoft® PowerPoint® attachments on the handheld
Workaround: Upgrade the BlackBerry Enterprise Server to version 4.0 SP1 HF1 or later before you upgrade the BlackBerry Enterprise Server to version 4.0 SP2. SDR 54329
When you install or upgrade the BlackBerry Enterprise Server, if the BlackBerry Enterprise Server name contains one or more spaces, the BlackBerry Enterprise Server cannot connect to the Messaging Agent and messages do not redirect to handhelds. SDR 48666
If you upgrade the BlackBerry Enterprise Server using the web upgrader, the web upgrader executable file does not extract the installation files correctly and the setup program does not start. SDR 40956
When you upgrade the BlackBerry Enterprise Server, user defined log levels are not preserved during the upgrade. You must redefine them manually. Wireless calendar synchronization: SDR 58220
In certain circumstances, when the organizer receives accepted meeting requests, the When field does not display correctly. SDR 57219
On certain BlackBerry Connect devices, when an organizer sends an updated meeting request from the handheld, and the attendee accepts the meeting request, the attendee’s status does not synchronize to the desktop computer correctly. SDR 55928
In certain circumstances, when a user tentatively accepts a meeting request, the status of the meeting displays as Busy. SDR 55785
If, in Outlook, a user declines or tentatively accepts an appointment occurrence in a recurring set of appointments after accepting the recurring set of appointments, the meeting request status does not update in the organizer’s calendar.
Workaround: Turn off wireless message redirection for the organizer, and the organizer’s calendar updates as expected. SDR 55112
In certain circumstances, if a user declines a recurring appointment, the handheld displays the incorrect date that the user declined the appointment. SDR 46626
In certain circumstances, users cannot accept a meeting request for a recurring meeting from their handhelds. SDR 45992
In certain circumstances, when an organizer sends a meeting request from the desktop computer to a handheld with a Busy status, the status of the meeting request displays as Tentative on the handheld. SDR 43520
When users create an appointment on the handheld and the BlackBerry Enterprise Server uses CDO version 6.5.6803.0, duplicate instances of the appointment might synchronize to the handheld. SDR 42689
When a user updates an occurrence of a recurring all day appointment from one time zone to another time zone on the handheld, the appointment does not update correctly in Outlook if the handheld and user desktop computer are situated in different time zones. Wireless enterprise activation: SDR 37897
In certain circumstances, if you assign and activate two different users on separate BlackBerry Enterprise Servers that both use the same configuration database, the user’s PIN might not synchronize between the user’s desktop computer and the configuration database correctly. Wireless message reconciliation: SDR 57467
In certain circumstances, if you add a disclaimer text message in the BlackBerry Manager, then attempt to delete the disclaimer, the text still displays in messages that are received on handhelds.