Noch vor kurzem habe ich darüber geschrieben, dass die Release Notes für das MR3 verfügbar sind und schon heute Abend durfte ich von Roland erfahren, dass das MR3 ab sofort auf den BlackBerry Supportseiten online gestellt worden ist.
Ihr solltet beachten, dass auch beim MR3 die gleichen Probleme wie bei der MR2 Installation auftauchen könnten, ich habe schon im Beitrag für die Release Notes darauf hingewiesen. Und nun kommen wir auch zum wichtigsten Teil, den Bugfixes bzw. den behobenen Problemen:
BlackBerry Administration Service
- When you run a cluster of three BlackBerry® Administration Service instances with one empty group and two groups with 1500 members, create a software configuration with two optional applications to be delivered wirelessly, assign the software configuration to the empty user group, and then change the two other groups to child groups of the empty group, the BlackBerry Administration Service writes SQL exceptions to the BlackBerry Administration Service log files and does not deliver the two applications to all of the users in the groups. (DT 348590)
- If the BlackBerry Administration Service – Native Code Container service on a computer that hosts the BlackBerry Administration Service is stopped for more than 110 minutes, the reconciliation process stops responding. (DT 450431)
- The BlackBerry® Enterprise Server might have stopped job reconciliation unexpectedly if the BlackBerry Administration Service singleton did not receive the close job message from the close job message queue. (DT 491377)
- In certain circumstances, the outstanding event count for internal reconciliation in the BlackBerry Administration Service was not zero and reconciliation was slow. (DT 502311)
- After you installed BlackBerry Enterprise Server MR1 on a computer that runs Windows® 2008, the BlackBerry Administration Service might have stopped responding. (SDR 332933)
- BlackBerry device users could not use chunked encoding when uploading files from a device to a remote file location. (DT 461732)
- In a BlackBerry Administration Service pool, when you set up many jobs for updating the BlackBerry® Device Software, certain jobs are not completed and remain in “ready to deliver” status. (DT 504114)
- In certain circumstances, in a BlackBerry Administration Service pool, the BlackBerry Administration Service does not reconcile applications and BlackBerry Device Software appropriately.(DT 503411)
- When batching users during reconciliation, the BlackBerry Administration Service tried to create duplicate records for some users, which caused errors and stopped reconciliation. (DT 509538)
- *When using multiple tabs in Windows® Internet Explorer® 7 to access the BlackBerry Administration Service, the information thatyou typed in one tab might have appeared in another tab. (DT 387664)
BlackBerry Attachment Service
- In certain circumstances, the BlackBerry Attachment Service could not successfully process attachments that included special characters. (DT 438458)
- BlackBerry Client for use with Microsoft Office Communications Server 2007
*If a user started a conversation from a BlackBerry® Client for use with Microsoft® Office Communications Server 2007, and the recipient responded to the message from the recipient’s BlackBerry Client for use with Microsoft Office Communications Server 2007, and then the recipient started a conversation with the user from the instant messaging client on the recipient’s computer, the user received the message as part of the pre-existing conversation and all the responses of the user were sent to the recipient’s BlackBerry Client for use with Microsoft Office Communications Server 2007 only. (DT 453062)
BlackBerry Collaboration Service
- *If you installed the BlackBerry Administration Service, BlackBerry Web Desktop Manager, BlackBerry Collaboration Service, and Microsoft® SQL Server® Express Edition on the same computer, the BlackBerry Collaboration Service did not start. (DT 521389)
BlackBerry Controller
- *When the BlackBerry Controller stopped, it did not use the timeout value of the AgentShutdownTimeout registry key. (DT 485302)
BlackBerry MDS Connection Service
- If a user’s password included special characters (for example, a colon), the BlackBerry MDS Connection Service could not log the user into sites. (DT 192247)
- *When a user tried to browse to an HTTPS site that uses a certificate that contains “Subject Alternative Name”, the BlackBerry device displayed an HTTP 500 error message and the BlackBerry MDS Connection Service wrote a java.lang.IndexOutOfBoundsException error to its log file. (DT 478993)
- *If you configured the BlackBerry MDS Connection Service to authenticate BlackBerry devices to content servers that use NTLMv2, and a user did not specify the Windows domain name when attempting to log in, the user was prompted again to specify login information. After several attempts, in certain circumstances, the user’s Windows account was locked. (DT 508292)
BlackBerry Messaging Agent
- In a Microsoft® Exchange 2010 environment, after you configured Microsoft® Exchange Web Services, a recurring meeting received on a BlackBerry device from Microsoft® Outlook® 2003 displayed as an email message. (DT 431390)
- In a Microsoft Exchange 2010 environment, the attachment icon did not appear with email messages on BlackBerry devices. (DT 431003)
- In a Microsoft Exchange 2010 environment, if users created memo or task subfolders on BlackBerry devices, the BlackBerry Messaging Agent stopped responding and users could not synchronize memos or tasks from BlackBerry devices. (DT 375634)
- In certain circumstances, when the BlackBerry Messaging Agent started and could not access public folders, the BlackBerry Messaging Agent could not perform free/busy lookups. (SDR 339968)
- When a BlackBerry device user selected the inbox and another folder for redirection and saved changes, selected the Sent Items folder for redirection and saved changes, and disabled and enabled wireless reconciliation, the redirection for the Sent Items folder was reverted back to its original state. (DT 357408)
- In previous releases, you could not configure the shutdown timer for the BlackBerry Messaging Agent. In this release, you can configure the AgentShutdownTimeout key in HKEY_LOCAL_MACHINE\SOFTWARE\Research In Motion\BlackBerry Enterprise Server\Agents. The default value is 40 (seconds). Permitted values are 40 or higher. The BlackBerry Controller adds 20 seconds to the value before it attempts to shut down the BlackBerry Messaging Agent. (DT 454733)
- *In certain circumstances, when you configure BlackBerry devices to synchronize with public folder contacts and then fail over to the standby BlackBerry Enterprise Server, the BlackBerry Messaging Agent stops unexpectedly. (DT 451637)
- *In high availability configurations, if the SCS Worker thread entered into a hung state while executing mailbox commands, all mail servers were not reported as unhealthy so no failover took place. (DT 486948)
- *When you restarted a domain controller that a Microsoft® Exchange Server used, the BlackBerry Messaging Agent might have stopped responding until the BlackBerry Controller restarted it. (DT 229353)
- *Invalid property values were passed into SetProps resulting in unneeded AV exceptions being generated within MAPI. (DT 529641)
- *When the BlackBerry Enterprise Server made calls to certain MAPI functions, the calls could result in non-fatal and handled exceptions. (DT 529638)
BlackBerry Monitoring Service
- In certain circumstances, after you installed a maintenance release, the BlackBerry Monitoring Service did not start. (DT 366027)
- *When you tried to save a server configuration that you edited, the BlackBerry Monitoring Service displayed a timeout error. (DT 509942)
- *When you created a report and clicked View generated reports immediately, the Generate graphics and Help links did not work and displayed an error message instead. (DT 536554)
BlackBerry Policy Service
- In certain circumstances, the BlackBerry Policy Service could take up to 12 hours to process work requests. (DT 391803)
- *When you added BlackBerry Administration Service instances to a BlackBerry Domain, IT policy reconciliation slowed. (DT 470586)
Calendar synchronization
- If a user used Microsoft® Outlook® 2007 and configured a delegate, the user received Informational Only messages as meeting invitations in Microsoft Outlook. (DT 425322)
Instant messaging
- In an environment that included Microsoft® Office Communications Server 2007, a BlackBerry device did not display unicode characters correctly in the Personal Note, Custom Location, and Custom Status fields. (DT 333275)
Organizer data synchronization
- In BlackBerry Enterprise Server 5.0 MR3, in certain circumstances, if you added a user, created a public contact folder on a Microsoft® Exchange Server that does not host the user, enabled synchronization for the public contact folder, synchronized a new contact for the user, changed the new contact’s named properties, and synchronized the contact again, the contact information might have been missing information or contained information in the wrong data fields. (DT 430602)
- If you included public folders for a BlackBerry device user and synchronized contacts from public folders to the device, the street name might not have appeared correctly. (DT 309220)
Setup application
- In certain circumstances, when you installed the maintenance release, the BlackBerry Enterprise Server version information was incorrect in Add/Remove Programs. (DT 365769)
- When you installed the previous maintenance release, the setup application did not register the EWS.dll and you could not use Microsoft® Exchange Web Services. (DT 304875)
- When you installed BlackBerry Enterprise Server MR1 on a computer that runs Windows 2008, the setup application could not stop the BlackBerry Attachment Monitoring Service and File Conversion Executable processes. (SDR 364395)
- When you ran the setup application for the maintenance release on Windows Server® 2008, a permissions conflict might have caused the setup application to close unexpectedly. (SDR 319193)
Download: BlackBerry Enterprise Server 5.0.1 MR3
Link: Release Notes (PDF)
Server | 7 Kommentare »