Blackberry ENTERPRISE SERVER FOR IBM LOTUS DOMINO - - MAINTENANCE RELEASE NOTES Catatan Rilis - Halaman 8

Jelajahi secara online atau unduh pdf Catatan Rilis untuk Server Blackberry ENTERPRISE SERVER FOR IBM LOTUS DOMINO - - MAINTENANCE RELEASE NOTES. Blackberry ENTERPRISE SERVER FOR IBM LOTUS DOMINO - - MAINTENANCE RELEASE NOTES 18 halaman. For ibm lotus domino
Juga untuk Blackberry ENTERPRISE SERVER FOR IBM LOTUS DOMINO - - MAINTENANCE RELEASE NOTES: Catatan Rilis (6 halaman)

Halaman Cetak

BlackBerry Enterprise Server version 4.1 SP6 for IBM Lotus Domino

BlackBerry Client for Novell GroupWise Messenger version 2.1.10

SDR 151305

In previous versions of the collaboration client, if a user changed their status to "Appear offline" while in a conversation,

the conversation window remained open, but the user could not send messages. If the user changed their status back to

"Online", the user could not be invited into the same conversation again.

In the BlackBerry Client for Novell GroupWise Messenger version 2.1.10, this issue is resolved.

SDR 132210

In previous versions of the collaboration client, users could not delete a personal group from their contact lists without

first deleting the individual members of the group.

In the BlackBerry Client for Novell GroupWise Messenger version 2.1.10, this issue is resolved.

SDR 75641

In previous versions of the collaboration client, when a user used the collaboration client to open a conversation with a

contact, then invited more contacts to join the conversation, an invitation was sent to all contacts. If a contact on a different

BlackBerry Enterprise Server refused the invitation, the user was unable to invite the contact to join the conversation

again.

In the BlackBerry Client for Novell GroupWise Messenger version 2.1.10, this issue is resolved.

BlackBerry Configuration Database

SDR 173385

In BlackBerry Enterprise Server version 4.1 SP4 and later, the BlackBerry database notification system might have

caused memory fragmentation in the Microsoft® SQL Server®.

In BlackBerry Enterprise Server version 4.1 SP6, this issue is resolved.

SDR 171648

In BlackBerry Enterprise Server version 4.1 SP4 and later, if you installed the BlackBerry database notification system

and cleared the statistics for one or more users, the BlackBerry database notification system might have caused

recomputations on the Microsoft SQL Server, resulting in high CPU usage.

In BlackBerry Enterprise Server version 4.1 SP6, this issue is resolved.

SDR 158538

In BlackBerry Enterprise Server version 4.1 SP4 and later, if you viewed the information for the BlackBerry

Configuration Database using your database management console, no information was available for the MDSdailyStat,

MDShourlyStat, and MDSmonthlyStat views.

In BlackBerry Enterprise Server version 4.1 SP6, this issue is resolved.

SDR 158473

In BlackBerry Enterprise Server version 4.1 SP4 and later, if Microsoft SQL Server 2005 Express Edition was installed

on the computer that hosted the BlackBerry Enterprise Server, the BlackBerry Enterprise Server services that were

dependent on the BlackBerry Configuration Database, including the BlackBerry Dispatcher, the BlackBerry

Synchronization Service, and the BlackBerry Policy Service, might have stopped responding or might not have started

successfully if you restarted Microsoft® Windows®.

In BlackBerry Enterprise Server version 4.1 SP6, this issue is resolved.

BlackBerry Configuration Panel

SDR 158898

In BlackBerry Enterprise Server version 4.1 SP5, after you installed the BlackBerry Enterprise Server, on the OTA WIFI

Activation tab in the BlackBerry Configuration Panel, you could not set an SMTP server port number lower than 1024.

You could set an SMTP server port number lower than 1024 during the initial setup program.

In BlackBerry Enterprise Server version 4.1 SP6, this issue is resolved.

BlackBerry Controller

SDR 165274

In BlackBerry Enterprise Server version 4.1 SP3 and later, the BlackBerry Controller did not detect when the timer thread

of the BlackBerry Messaging Agent stopped responding. As a result, the BlackBerry Controller did not restart the

BlackBerry Messaging Agent when the timer thread stopped responding.

In BlackBerry Enterprise Server version 4.1 SP6, this issue is resolved.

SDR 149511

In previous versions of the BlackBerry Enterprise Server, if threads became hung, after those threads reached a waitcount

of 2, the BlackBerry Enterprise Server might not have printed a stack trace.

In BlackBerry Enterprise Server version 4.1 SP6, this issue is resolved.

SDR 141675

In previous versions of the BlackBerry Enterprise Server, the BlackBerry Controller did not reset the heartbeat count when

it restarted the BlackBerry Messaging Agent. As a result, if there was a delay when you restarted the BlackBerry

Messaging Agent, the BlackBerry Controller might have continuously restarted the BlackBerry Messaging Agent.

In BlackBerry Enterprise Server version 4.1 SP6, this issue is resolved.

SDR 133464

In previous versions of the BlackBerry Enterprise Server, in certain circumstances, the BlackBerry Controller might have

restarted the BlackBerry Messaging agent due to thread optimization issues.

In BlackBerry Enterprise Server version 4.1 SP6, this issue is resolved.