View Single Post
Old 09-12-2006, 11:34 PM   #2 (permalink)
jibi
BlackBerry God
 
jibi's Avatar
 
Join Date: Oct 2004
Location: Jibi's Secret Place
Model: 8900
OS: 4.6.1.174
Carrier: AT&T
Posts: 11,310
Post Thanks: 0
Thanked 1 Time in 1 Post
Default

Fixed issues
BlackBerry Collaboration Service
SDR 91492
In BlackBerry Enterprise Server 4.1 and later, if your instant messaging environment is Novell ® GroupWise® Messenger, if a userxxx8217;s BlackBerry device is using French and the user sends an instant message that contains accented characters to a BlackBerry device that uses English, the characters in the instant message are displayed on the recipientxxx8217;s BlackBerry device incorrectly.

In BlackBerry Enterprise Server Version 4.1 SP2, this issue is resolved.

SDR 90928
In BlackBerry Enterprise Server 4.1 and later, if your instant messaging environment is IBM® Lotus® Sametime® and your IBM Lotus Domino® environment is configured to resolve multiple names to a single lookup (for example, performing a directory assistance lookup using a local names.nsf file on each IBM Lotus Domino server and a consolidated Notes Address Book), users cannot log in to enterprise messenger because two names are returned during authentication to the BlackBerry Collaboration Service instead of one.

In BlackBerry Enterprise Server Version 4.1 SP2, this issue is resolved.

BlackBerry Configuration Database
SDR 95374
In BlackBerry Enterprise Server Version 4.1 and later, if you click Reset PIM Sync Global Field Mapping, the Address Book fields return to default Microsoft Exchange values because of an incorrect database script.

In BlackBerry Enterprise Server Version 4.1 SP2, this issue is resolved.

SDR 92316
In BlackBerry Enterprise Server Version 4.1 and later, in certain circumstances, Microsoft SQL Server statements might place a large amount of load on the Microsoft SQL Server.

In BlackBerry Enterprise Server Version 4.1 SP2, this issue is resolved.

SDR 90032
In BlackBerry Enterprise Server Version 4.1 and later, the user is unable to install Database Notification System (DBNS) on the Microsoft SQL Server with the named instance.

In BlackBerry Enterprise Server Version 4.1 SP2, this issue is resolved.

SDR 87442
In BlackBerry Enterprise Server Version 4.1 and later, the BlackBerry Configuration Database creation fails if you assign a long name to the database.

In BlackBerry Enterprise Server Version 4.1 SP2, this issue is resolved.

SDR 79960
In BlackBerry Enterprise Server Version 4.1 and later, if you remove the last blank line from the BESMgmt.cfg file, the CreateDB tool does not start successfully.

In BlackBerry Enterprise Server Version 4.1 SP2, this issue is resolved.

BlackBerry Dispatcher
SDR 89503
In BlackBerry Enterprise Server Version 4.1, not all BlackBerry Dispatcher disconnects are logged at level [20000] with a unique event ID in the log files.

In BlackBerry Enterprise Server Version 4.1 SP2 and later, this issue is resolved.

SDR 86413
In BlackBerry Enterprise Server Version 4.1 and later, if the BlackBerry Dispatcher uses multiple threads to start SRP connections through the BlackBerry Router, and only one connection is successful, the BlackBerry Dispatcher does not re-attempt to start the additional connections. In BlackBerry Enterprise Server environments where you have a primary SRP connection and secondary SRP connections (for example, a BlackBerry Enterprise Server upgraded from Version 3.6 to Version 4.1), users mapped to the secondary SRP connection can receive messages but cannot send messages.

In BlackBerry Enterprise Server Version 4.1 SP2, this issue is resolved.

SDR 81898
In BlackBerry Enterprise Server Version 4.1 and later, when you create user accounts on the same messaging server and the user accounts are assigned to BlackBerry Messaging Agents, if the BlackBerry Messaging Agents have ServerDN values of characters that are not the same case (for example, ServerDN=/O= and ServerDN=/o=), the user accounts are not grouped together on the same BlackBerry Messaging Agent.

In BlackBerry Enterprise Server Version 4.1 SP2, this issue is resolved.

BlackBerry Instant Messaging for GroupWise
SDR 78817
Previously, if users were in a conversation with a contact who did not appear in their contact list, and they deleted that conversation, but the contact continued to send instant messages, an xxx8220;Uncaught exceptionxxx8221; error message appeared.

SDR 72025
Previously, if users were using a BlackBerry device with BlackBerry Device Software version 4.1, the Enterprise Messenger typing indicators and xxx8220;Message Receivedxxx8221; pop up messages might not have appeared.

BlackBerry Instant Messaging for Live Communications Server
SDR 80118
Previously, if users were using Microsoft Windows® Messenger, and they tried to switch conversations using the message indicator, a xxx8220;message queue overflowxxx8221; error message appeared.

BlackBerry MDS Connection Service
SDR 80201
In BlackBerry enterprise Server Version 4.1 and later, if you changed the properties for a BlackBerry MDS Connection Service, the changes were not saved.

In the BlackBerry Enterprise Server Version 4.1 SP2 and later, this issue is resolved.

SDR 78922
In the BlackBerry Enterprise Server Version 4.1, if you created a BlackBerry MDS Connection Server access control push rule with the same name as an access control pull rule, an application error appeared. The same behavior occurred if you created a pull rule with the same name as a push rule.

In the BlackBerry Enterprise Server Version 4.1 SP2 and later, this issue is resolved.

BlackBerry MDS Services
SDR 100855
In BlackBerry Enterprise Server Version 4.1 and later, if you remove a BlackBerry MDS Studio Application, the application record is not removed from the BlackBerry MDS Application Repository.

In the BlackBerry Enterprise Server Version 4.1 SP2, this issue is resolved.

SDR 88104
In the BlackBerry Enterprise Server Version 4.1 SP1, the BlackBerry MDS Services Properties page title contained unnecessary padding before xxx8220;(Audit Only)xxx8221; appeared.

In the BlackBerry Enterprise Server Version 4.1 SP2, this issue is resolved.

BlackBerry Manager
SDR 91948
In BlackBerry Enterprise Server Version 4.1 and later, if you resend service books to multiple users at once, you must click OK for each user.

In BlackBerry Enterprise Server Version 4.1 SP2, this issue is resolved.

SDR 91507
In BlackBerry Enterprise Server Version 4.1 and later, junior help desk administrators cannot access the Devices Registered properties dialogs. This administrator role should have xxx8220;Deletexxx8221; permission for this screen.

In BlackBerry Enterprise Server Version 4.1 SP2, this issue is resolved.

SDR 89278
In BlackBerry Enterprise Server Version 4.1 and later, if you select a user on the Users tab, click Assign to Group, and then click OK without selecting a group for the user, an SQL error appears in the BlackBerry Manager log file.

In BlackBerry Enterprise Server Version 4.1 SP2, this issue is resolved.

SDR 87628
In BlackBerry Enterprise Server Version 4.1 and later, on the Global Properties dialog, the Push Control description has a typo that reads Blackberry MDS Connection Service xxx8230;.xxx8221;

In BlackBerry Enterprise Server Version 4.1 SP2, this issue is resolved.

SDR 87609
In BlackBerry Enterprise Server Version 4.1 and later, if you set an enterprise activation password to expire at a time other than the default (48 hours), the expiry time reverts to the default after you close the Set Activation Password dialog and re-open it.

In BlackBerry Enterprise Server Version 4.1 SP2, this issue is resolved.

SDR 87592
In BlackBerry Enterprise Server Version 4.1 and later, if you create a BlackBerry MDS Connection Service push rule with the same name as an existing pull rule, an error message indicates that the name already exists and an application error appears.

In BlackBerry Enterprise Server Version 4.1 SP2, this issue is resolved.

SDR 87255
In the Device Policies properties dialog on the MDS Services tab, the Allow Push Application Install option displays the incorrect UI description.

In BlackBerry Enterprise Server Version 4.1 SP2, this issue is resolved.

SDR 85927
In BlackBerry Enterprise Server Version 4.1, if you are using database authentication to connect the BlackBerry Manager to the BlackBerry Configuration Database, and the credentials you supply are not accepted, the BlackBerry Manager does not clear the login credential stored in the registry.

In BlackBerry Enterprise Server Version 4.1 SP2, this issue is resolved.

SDR 82677
In BlackBerry Enterprise Server Version 4.1 and later, in some circumstances, if you highlight a user name on the Users tab when there is only one user on the BlackBerry Enterprise Server, the user name might appear multiple times in the bottom pane of the Users tab.

In BlackBerry Enterprise Server Version 4.1 SP2, this issue is resolved.

SDR 80832
In BlackBerry Enterprise Server Version 4.1 and later, senior help desk administrators have read-only access to the Add Users dialog on the Servers tab, but full access to the Add Users dialog on the Users tab. This administrator role should have full access to the Add User dialog in all circumstances.

In BlackBerry Enterprise Server Version 4.1 SP2, this issue is resolved.

SDR 80328
In BlackBerry Enterprise Server Version 4.1 and later, if a junior help desk administrator logs in to a remote BlackBerry Manager, this administrator can access and perform the Move User action. This option should be hidden from this administrator role.

In BlackBerry Enterprise Server Version 4.1 SP2, this issue is resolved.

SDR 80244
In BlackBerry Enterprise Server Version 4.1 and later, a Clear Statistics option link incorrectly appears on the Collaboration Service tab. This link does not provide any functionality.

In BlackBerry Enterprise Server Version 4.1 SP2, this issue is resolved.

SDR 79622
In BlackBerry Enterprise Server Version 4.1 and later, audit security administrators can perform the Export Stats to File task on the Users tab. This administrator role should not have permission to perform this task.

In BlackBerry Enterprise Server Version 4.1 SP2, this issue is resolved.

SDR 79600
In BlackBerry Enterprise Server Version 4.1 and later, if you assign a user to a group when no other groups exist in the BlackBerry Domain, an incorrect error message (xxx8220;There are no other groups to copy properties toxxx8221;) appears.

In BlackBerry Enterprise Server Version 4.1 SP2, this issue is resolved.

SDR 79532
In BlackBerry Enterprise Server Version 4.1 and later, in some circumstances, the Set Activation Password option does not appear on the User Groups List tab.

In BlackBerry Enterprise Server Version 4.1 SP2, this issue is resolved.

SDR 78256
In BlackBerry Enterprise Server Version 4.1 and later, if an audit security administrator attempts to map a global IT policy to a user, an application error occurs.

In BlackBerry Enterprise Server Version 4.1 SP2, this issue is resolved.

SDR 77401
In BlackBerry Enterprise Server Version 4.1 and later, if you assign an invalid PIN number to a BlackBerry MDS Services message monitor definition, an application error message appears.

In BlackBerry Enterprise Server Version 4.1 SP2, this issue is resolved.

SDR 77233
In BlackBerry Enterprise Server Version 4.1 and later, if you change the BlackBerry MDS Connection Service server host name to a URL that does not exist, an application error message appears.

In BlackBerry Enterprise Server Version 4.1 SP2, this issue is resolved.

SDR 77176
In BlackBerry Enterprise Server Version 4.1 and later, if the BlackBerry MDS Services is installed on a remote computer, and you create a new BlackBerry MDS Services device policy but leave the Policy Name field blank, an application error appears and the BlackBerry Manager might stop responding.

In BlackBerry Enterprise Server Version 4.1 SP2, this issue is resolved.

SDR 76827
In BlackBerry Enterprise Server Version 4.1 and later, in certain circumstances, when two BlackBerry Enterprise Servers share the same BlackBerry Configuration Database, if you attempt to clear the user statistics, only some of the statistics are successfully removed.

In BlackBerry Enterprise Server Version 4.1 SP2, this issue is resolved.

SDR 76812
In BlackBerry Enterprise Server Version 4.1 and later, in some circumstances, if you create a user group of multiple users and then export the user group statistics to a text file, the text file displays the correct statistics from the BlackBerry Manager for the first user in the list, but replicates the same information for the remaining users.

In BlackBerry Enterprise Server Version 4.1 SP2, this issue is resolved.

BlackBerry Messaging Agent
SDR 97292
In BlackBerry Enterprise Server Version 4.1 and later, if you attach a contact whose name contains an accented character to an email, the BlackBerry Messaging Agent does not deliver the attachment to a userxxx8217;s BlackBerry device.

In BlackBerry Enterprise Server Version 4.1 SP2, this issue is resolved.

SDR 95171
In BlackBerry Enterprise Server Version 4.1 and later, the BlackBerry Controller monitors the BlackBerry Messaging Agentxxx8217;s health by sending a status query every 10 minutes. The BlackBerry Messaging Agent does not respond to the BlackBerry Controllerxxx8217;s initial status query if it experiences a higher than normal load when starting a large number of users. As a result, the BlackBerry Controller logs a warning message in the log file. If the BlackBerry Messaging Agent does not respond to the second status query, the BlackBerry Messaging Agent might restart.

In BlackBerry Enterprise Server Version 4.1 SP2, this issue is resolved.

SDR 92882
In BlackBerry Enterprise Server Version 4.1 and later, if users have multiple folders enable for redirection and then switch devices, during message prepopulation the BlackBerry Enterprise Server reports a xxx8220;GetContentsTable (0x80004005) failedxxx8221; error in the log file. During subsequent rescans for message reconciliation, the BlackBerry Messaging Agent receives a xxx8220;LowLevelErrorxxx8221; error from the messaging server and the userxxx8217;s account becomes inactive.

In BlackBerry Enterprise Server Version 4.1 SP2, this issue is resolved.

SDR 91864, SDR 90852
In BlackBerry Enterprise Server Version 4.1 and later, if you enable the HostedServer registry key, the BlackBerry Messaging Agent does not return distribution lists in the results of address lookups, and users cannot send messages to distribution lists from their BlackBerry devices.

In BlackBerry Enterprise Server Version 4.1 SP2, this issue is resolved.

SDR 90872
In BlackBerry Enterprise Server Version 4.1 and later, in certain circumstances, long running operations (for example, synchronizing an Address Book with a large number of items) might cause loops that do not update the thread health state. As a result, mail flow delays might occur, the log files might display multiple hung threads, and the BlackBerry Enterprise Server might restart the BlackBerry Messaging Agent continuously.

In BlackBerry Enterprise Server Version 4.1 SP2, this issue is resolved.

SDR 90585
In BlackBerry Enterprise Server Version 4.1 and later, the BlackBerry Messaging Agent prevented BlackBerry Connectxxx8482; device users from viewing attachments that were larger than 32 KB in size.

In BlackBerry Enterprise Server Version 4.1 SP2, BlackBerry Connect device users can view attachments that are up to 60 KB in
size.

SDR 90567
In BlackBerry Enterprise Server Version 4.1 and later, when the BlackBerry Messaging Agent writes event [15010] to the log file, it writes xxx8220;(Reserved)xxx8221; instead of the actual error.

In BlackBerry Enterprise Server Version 4.1 SP2, this issue is resolved.

SDR 88012
In BlackBerry Enterprise Server Version 4.1 and later, if the BlackBerry Messaging Agent issues a stop command to a worker thread during threadpool optimization and does not receive a response, the BlackBerry Messaging Agent continues to wait indefinitely for a response.

In BlackBerry Enterprise Server Version 4.1 SP2, this issue is resolved.

SDR 88008
In BlackBerry Enterprise Server Version 4.1 and later, if you reassign a BlackBerry device to a new user while the BlackBerry Enterprise Server for the previous userxxx8217;s account is located is temporarily shut down, when you turn the BlackBerry Enterprise Server back on, it might try to reclaim the BlackBerry device for the previous user.

In BlackBerry Enterprise Server Version 4.1 SP2, this issue is resolved.

SDR 87924
In BlackBerry Enterprise Server Version 4.1 and later, if two threads attempt to create a timer at the same time, one thread might stop responding.

In BlackBerry Enterprise Server Version 4.1 SP2, this issue is resolved.

SDR 86287
In BlackBerry Enterprise Server Version 4.1 and later, the BlackBerry Messaging Agent does not report the Server DN or the SRP Routing Info immediately after a restart.

In BlackBerry Enterprise Server Version 4.1 SP2, this issue is resolved.

SDR 85727
In BlackBerry Enterprise Server Version 4.1 and later, if you install the BlackBerry Enterprise Server with an evaluation license key while the Simple Network Management Protocol (SNMP) services is running, license information values in the BlackBerry Enterprise Server Management Information Base (MIB) file for dispConfigLicenseTotal, dispConfigLicenseUsed, and dispConfigLicenseRemaining are not correct.

In BlackBerry Enterprise Server Version 4.1 SP2, this issue is resolved.

SDR 85368
In BlackBerry Enterprise Server Version 4.1 and later, if you change the importance of a global filter to any value other than xxx8220;Nonexxx8221;, the BlackBerry Messaging Agent ignores the filter and forwards the entire message to usersxxx8217;s BlackBerry devices.

In BlackBerry Enterprise Server Version 4.1 SP2, this issue is resolved.

SDR 82377
In BlackBerry Enterprise Server Version 4.1 and later, if you quickly file more than 10 messages into a subfolder in the Inbox of your desktop email program, the BlackBerry Messaging Agent does not detect the moves of the 11th and later messages so does not reconcile them to your BlackBerry device.

In BlackBerry Enterprise Server Version 4.1 SP2, this issue is resolved.

SDR 77835
In BlackBerry Enterprise Server Version 4.1 and later, if the BlackBerry Messaging Agent is unable to retrieve an updated folder list for a user account from the messaging server (for example, if a brief network error occurs), then messages filed on the userxxx8217;s desktop email program do not reconcile and the messages remain in the Inbox on the userxxx8217;s BlackBerry device until the next attempt to retrieve the folder lists occurs.

In BlackBerry Enterprise Server Version 4.1 SP2, this issue is resolved.

SDR 68494
In BlackBerry Enterprise Server Version 4.1 and later, if you stop and restart the BlackBerry Controller from the Microsoft Windows Services pane, information is not written to the SNMP trap watcher.

In BlackBerry Enterprise Server Version 4.1 SP2, this issue is resolved.

SDR 48874
In BlackBerry Enterprise Server Version 4.1 and later, if a user replaces a valid email address with an incorrect email address in the address book on the BlackBerry device, an email message sent to the incorrect address does not bounce back and might be sent to another email address that partly matches the incorrect email address.

In BlackBerry Enterprise Server Version 4.1 SP2, this issue is resolved.

BlackBerry Policy Service
SDR 90650
In BlackBerry Enterprise Server Version 4.1 and later, in certain circumstances, the BlackBerry Policy Service stops responding if it processes an IT Policy incorrectly.

In BlackBerry Enterprise Server Version 4.1 SP2, this issue is resolved.

SDR 85151
In BlackBerry Enterprise Server Version 4.1 and later, under some circumstances, the BlackBerry Policy Service might automatically requeue the IT policy to be resent to the BlackBerry device every 30 minutes if the BlackBerry device does not acknowledge receipt of the IT policy.

In BlackBerry Enterprise Server Version 4.1 SP2, this issue is resolved.

Setup program
SDR 80402
In BlackBerry Enterprise Server Version 4.1 and later, you did not have the option to change to a new BlackBerry ConfigurationDatabase using the BlackBerry Configuration Panel on a computer where you installed only the BlackBerry Collaboration Service.

In BlackBerry Enterprise Server Version 4.1 SP2, this issue is resolved.

SDR 79844
In BlackBerry Enterprise Server Version 4.1 and later, if you enter the SRP address with spaces, you cannot validate the SRP ID and key.

In BlackBerry Enterprise Server Version 4.1 SP2, this issue is resolved.

SDR 78977
In BlackBerry Enterprise Server Version 4.1 and later, when you upgraded the BlackBerry Enterprise Server the setup program selected Windows authentication as the default authentication method to the BlackBerry Configuration database. If you had previously selected database authentication when installing the BlackBerry Enterprise Server, this choice was not detected by the setup program.

In BlackBerry Enterprise Server Version 4.1 SP2, this issue is resolved.

SDR 77498 In BlackBerry Enterprise Server Version 4.1 and later, when upgrading the BlackBerry Enterprise Server with BlackBerry MDS Services, the BlackBerry MDS Services might start after the BlackBerry Enterprise Server restarts during the upgrade and the setup program cannot complete successfully.

In BlackBerry Enterprise Server Version 4.1 SP2, this issue is resolved.

SDR 68142
In BlackBerry Enterprise Server Version 4.1 and later, you had to perform manual steps after completing the setup program to associate a BlackBerry Enterprise Server with an instance of BlackBerry MDS Services.

In BlackBerry Enterprise Server Version 4.1 SP2, this issue is resolved.

SDR 65361
In BlackBerry Enterprise Server Version 4.1 and later, the setup program does not validate the proxy connection information that you type to confirm that the information is expected (for example, numbers in the port field).

In BlackBerry Enterprise Server Version 4.1 SP2, this issue is resolved.

SDR 64673
In BlackBerry Enterprise Server Version 4.1 and later, the setup program did not confirm that the account with which you installed the BlackBerry Enterprise Server was part of the Local Administration group.

In BlackBerry Enterprise Server Version 4.1 SP2, this issue is resolved.

Wireless calendar synchronization
SDR 93190
In BlackBerry Enterprise Server 4.1 and later, if a meeting organizer adds a new invitee to a recurring meeting that has exceptions, the invitee is not added to the exceptions on the organizerxxx8217;s BlackBerry device.

In BlackBerry Enterprise Server Version 4.1 SP2, this issue is resolved.

SDR 89890
In BlackBerry Enterprise Server 4.1 and later, when a meeting invitee receives a meeting request on their BlackBerry device, the BlackBerry Messaging Agent writes an xxx8220;Attachment=RIM-Calendar, Extension is not validxxx8221; error message in the log file even though the meeting delivery was successful.

In BlackBerry Enterprise Server Version 4.1 SP2, this issue is resolved.

SDR 89411
In BlackBerry Enterprise Server Version 4.1 and later, if a user sends a meeting invitation to a large number of individual invitees (for example, 8000 people), the BlackBerry Messaging Agent uses unexpectedly high amounts of system resources.

In BlackBerry Enterprise Server Version 4.1 SP2, this issue is resolved.

SDR 89100
In BlackBerry Enterprise Server Version 4.1 SP1, if a meeting organizer updates an existing meeting from their BlackBerry device, changing both the subject of the meeting and changing the recurrence from a simple to a recurring meeting, the BlackBerry Messaging Agent reconciles the previous subject to both the organizerxxx8217;s desktop email program and to attendeesxxx8217; BlackBerry devices.

In BlackBerry Enterprise Server Version 4.1 SP2, this issue is resolved.

SDR 88742
In BlackBerry Enterprise Server Version 4.1 SP1, if an attendee tentatively accepts a meeting request but is subsequently removed from the list of attendees, the meeting is removed from the attendeexxx8217;s calendar on the BlackBerry device, but the attendeexxx8217;s status might still appear as Invited on the organizerxxx8217;s BlackBerry device.

In BlackBerry Enterprise Server Version 4.1 SP2, this issue is resolved.

SDR 87950
In BlackBerry Enterprise Server Version 4.1 and later, an organizerxxx8217;s meeting update might be unsuccessful if the sequence number of the meeting on the BlackBerry device is higher than the sequence number of the meeting on the messaging server (for example, if an organizer updates a meeting while their BlackBerry device is outside of a wireless coverage area and at the same time invitees are sending acceptances to the original meeting). The BlackBerry Messaging Agent is processing the meeting acceptance to the new appointment sent from the inviteexxx8217;s BlackBerry device, so the messaging server does not send the update from the meeting organizer.

In BlackBerry Enterprise Server Version 4.1 SP2, meeting invitees receive the organizerxxx8217;s update successfully and respond to the updated meeting.

SDR 87681
In BlackBerry Enterprise Server Version 4.1 and later, if a meeting organizer edits the location of an instance of a recurring meeting on their BlackBerry device, when an attendee tentatively accepts the meeting the BlackBerry Messaging Agent sends the acceptance to the organizer, but the attendeexxx8217;s status continues to display as Invited rather than Accepted in the calendar on their BlackBerry device.

In BlackBerry Enterprise Server Version 4.1 SP2, this issue is resolved.

SDR 86464
In BlackBerry Enterprise Server 4.1 and later, if an invitee accepts a meeting request from their desktop email program while message redirection is turned off on their BlackBerry device, when they re-enable message redirection, the BlackBerry Messaging Agent does not reconcile the meeting to their BlackBerry device.

In BlackBerry Enterprise Server Version 4.1 SP2, this issue is resolved.

SDR 76274
In BlackBerry Enterprise Server 4.1 and later, if an invitee attempts to accept a meeting on their BlackBerry device after the organizer cancels the meeting, the Blackberry device does not send the acceptance but the BlackBerry Messaging Agent does not delete the meeting, so the meeting appears in the calendar on the userxxx8217;s BlackBerry device.

In BlackBerry Enterprise Server Version 4.1 SP2, this issue is resolved.

The following issues are believed to be fixed in this software release, but have not been confirmed to be closed:

BlackBerry Configuration Database
SDR 98201
In BlackBerry Enterprise Server Version 4.1 and later, the BlackBerry Configuration Database logged communication errors using only hexidecimal numbers instead of text explaining the error.

SDR 97058
In BlackBerry Enterprise Server Version 4.1 and later, you cannot specify a path at the command prompt to the BESMgmt.cfg file when using the CreateDB tool. You were required to change the script root directory in the BESMgmt.cfg file instead.

SDR 94195
In BlackBerry Enterprise Server Version 4.1 and later, if you attempt to upgrade the BlackBerry Configuration Database and you have changed the machine name of the computer since creating the BlackBerry Configuration Database, the upgrade will not complete successfully.

SDR 91448
In BlackBerry Enterprise Server Version 4.1 and later, when you install a version of the BlackBerry Enterprise Server and specify a BlackBerry Configuration Database that is at a higher version (for example, a BlackBerry Enterprise Server Version 4.1 SP1 and a BlackBerry Configuration Database Version 4.1 SP2), the BlackBerry Configuration Database reports that the schema is not at the most current version. When the setup program checks the IsCurrent value, the BlackBerry Configuration Database supplies False instead of True.

SDR 91443
In BlackBerry Enterprise Server Version 4.1 and later, if the BlackBerry Configuration Database contains multiple entries in certain database tablesxxx8212;an expected result of merging two BlackBerry Configuration Databases into onexxx8212;the database job that purges BlackBerry MDS Connection Service messages does not complete successfully.

BlackBerry Manager
SDR 95479
In BlackBerry Enterprise Server Version 4.1 and later, when you remove a user account from the BlackBerry Enterprise Server, the user account is not removed from the BlackBerry MDS Server.

SDR 93907
In the BlackBerry Enterprise Server Version 4.1, you cannot send PIN messages from the BlackBerry Manager to users on the BlackBerry Enterprise Server Version 4.0.x, even if the users are in the same database.

SDR 92087
In BlackBerry Enterprise Server Version 4.1 and later, if you add two versions of the same application to a new software configuration, you do not receive an error indicating that this action is not supported. You receive an error only when you edit the software configuration.

SDR 89385
In BlackBerry Enterprise Server Version 4.1 and later, if you define two URL patterns with the same value in the URL Pattern fields but different service names (for example, HTTP and HTTPS), you receive an error message indicating that the URL pattern already exists.

SDR 89126
In BlackBerry Enterprise Server Version 4.1 and later, if you are using Microsoft Live Communication Server as your instant messaging server, you cannot specify a host name containing particular characters (for example, underscores) for the Live Communication Server service during the BlackBerry Enterprise Server installation. You can specify a host name containing these special characters in the BlackBerry Manager after the installation.

SDR 88816
In BlackBerry Enterprise Server Version 4.1 and later, the BlackBerry Manager shuts down unexpectedly if you create a software configuration that points to the Universal Naming Convention (UNC) path on a remote location, and the UNC path is changed.

SDR 88281
In BlackBerry Enterprise Server Version 4.1 and later, the notification icon is missing from the Monitor Messages window.

SDR 88155
In BlackBerry Enterprise Server Version 4.1 and later, the Local Access Control properties dialog for the BlackBerry MDS Connection Service incorrectly appears in the BlackBerry Collaboration Service properties dialog.

SDR 88002
In BlackBerry Enterprise Server Version 4.1 and later, if you create a pull rule with a name that is longer than 40 characters, an application error occurs.

SDR 86497
In BlackBerry Enterprise Server Version 4.1 and later, if you change an SRP identifier to an invalid SRP identifier, and then change the invalid SRP identifier back to the original identifier, the usersxxx8217; service books are not updated and users cannot send or receive messages on their BlackBerry devices.

SDR 86049
In BlackBerry Enterprise Server Version 4.1 and later, security administrators cannot view the Query Device Status option on the Devices Registered screen.

SDR 85207
In BlackBerry Enterprise Server Version 4.1 and later, if you upgrade BlackBerry Enterprise Server Version 4.0.4 to Version 4.1, and you are using a local Microsoft SQL Server 2000 SP3a database, you might be prompted for an SQL authentication password when you open the BlackBerry Manager. When you enter the SQL authentication password, the password does not function as expected.

SDR 82613
In BlackBerry Enterprise Server Version 4.1, the BlackBerry Manager starts when it is connected to a BlackBerry Configuration Database of an earlier version.

SDR 81035
In BlackBerry Enterprise Server Version 4.1 and later, if you used the Monitor Messages window to change the search criteria and then search for a BlackBerry device, the link that displayed in the BlackBerry Manager might have been broken.

SDR 80687
In BlackBerry Enterprise Server Version 4.1 and later, the feature to query the status of a BlackBerry device is missing from the BlackBerry Manager.

SDR 80383
In BlackBerry Enterprise Server Version 4.1 and later, BlackBerry device administrators could add, copy, and modify software configuration details when they should have read-only permission.

SDR 80350
In BlackBerry Enterprise Server Version 4.1 and later, BlackBerry device administrators and audit BlackBerry device administrators could access several dialogs for which they should have read-only permission on the Servers tab and User Groups List tab.

SDR 79196
In BlackBerry Enterprise Server Version 4.1 and later, in certain circumstances, when two BlackBerry Enterprise Servers share the same BlackBerry Configuration Database, if you use the BlackBerry Manager on one BlackBerry Enterprise Server to find a user on another BlackBerry Enterprise Server, user status information displays momentarily and then is not visible.

SDR 78771
In BlackBerry Enterprise Server Version 4.1 and later, in certain circumstances, when you schedule the date and time to send a BlackBerry MDS Studio application installation or upgrade to a BlackBerry device, the user receives an error on the BlackBerry device and the application does not install.

Workaround: Deselect the Schedule check box in the BlackBerry Manager and push the BlackBerry MDS Studio application to the BlackBerry device immediately.

SDR 77569
In BlackBerry Enterprise Server Version 4.1 and later, if you create message monitors to monitor BlackBerry MDS Services message traffic, the monitors do not persist in the BlackBerry Manager.

BlackBerry Messaging Agent
SDR 91390
In BlackBerry Enterprise Server Version 4.1 and later, in certain circumstances, a negative value is written to the MsgsFiltered field of the UserStats table. When the BlackBerry Messaging Agent attempts to update that userxxx8217;s statistics, an error occurs ({0x1640} PMDatabaseSQLImp::SetAllStatProps: COM Error 0x80040E57 - IDispatch error #3159 - Source: xxx8220;Microsoft OLE DB Provider for SQL Serverxxx8221; - Description xxx8220;Arithmetic overflow error converting expression to data type int.xxx8221; - Command "").

Workaround: Move the user to a new BlackBerry Messaging Agent where they are the only user.

BlackBerry Policy Service
SDR 92959
In BlackBerry Enterprise Server Version 4.1 and later, the last history ID for each IT Policy is stored in the registry and used by the change detection code as an index into the ServerConfigHistory. If you start the BlackBerry Enterpriser Server, and that registry key is not present on the computer, the BlackBerry Policy Service must rescan the entire ServerConfigHistory table of the BlackBerry Configuration Database.

SDR 75547
In BlackBerry Enterprise Server Version 4.1 and later, if the network connection between the BlackBerry Enterprise Server and the BlackBerry Configuration Database is unfavorable, the BlackBerry Policy Service might use increased system resources when determining whether users require upgrades to the applications on their BlackBerry devices.

SDR 66441
In BlackBerry Enterprise Server Version 4.1 and later, the IT policy log line is set to level 2 instead of level 4.

Setup program
SDR 95096
In BlackBerry Enterprise Server Version 4.1 and later, if more than one IP is connected to a single network card then the setup program terminates unexpectedly while gathering the network information.

SDR 90985
In BlackBerry Enterprise Server Version 4.1 SP1, if you installed a BlackBerry Router on a remote computer and then performed an upgrade of the BlackBerry Enterprise Server, the setup program configured the BlackBerry Enterprise Server to use the local BlackBerry Router.

SDR 90656
In BlackBerry Enterprise Server Version 4.1 and later, if your database environment is Microsoft SQL Server 2000 Database Engine (MDSE), during an upgrade of the BlackBerry Enterprise Server from Version 4.1 to Version 4.1 SP1, after you restart the computer and continue the upgrade, the License Key field is empty.

SDR 90540
In BlackBerry Enterprise Server Version 4.1 and later, if you are performing an upgrade using database authentication and the database credentials previously used to connect to the BlackBerry Configuration Database are missing from the registry, the upgrade fails with an xxx8220;Unable to get all Necessary Database Informationxxx8221; error.

SDR 89855
In BlackBerry Enterprise Server Version 4.1 and later, if you are upgrading the BlackBerry Enterprise Server from versions earlier than 4.0 SP4 to Version 4.1 SP1, settings customized within the BlackBerry Services are not preserved. These settings include the General, Log On and the Recovery tabs found under the properties of a BlackBerry service.

SDR 87626
In BlackBerry Enterprise Server Version 4.1 and later, if you are performing an upgrade using database authentication, and the setup program cannot locate the database credentials to perform the configuration portion of the upgrade, the setup program reverts to Windows authentication. If the administrative account with which you are performing the upgrade does not have permission to access the database server where you installed the BlackBerry Configuration Database, you receive a xxx8220;Failed to write License key to the Databasexxx8221; error message and cannot continue with the upgrade process.

SDR 87519
In BlackBerry Enterprise Server Version 4.1 and later, if the administrative account with which you complete the setup program has a password that includes quotations, the setup program does not complete successfully.

SDR 82682
In BlackBerry Enterprise Server Version 4.1 and later, you had the option to create a new BlackBerry Configuration Database during an upgrade instead of upgrading the existing BlackBerry Configuration Database.

SDR 81444
In BlackBerry Enterprise Server Version 4.1 and later, if you upgrade the BlackBerry Enterprise Server Version 3.6 SP6 to Version 4.1, image attachments attached to email messages that are sent to the BlackBerry device do not appear in the Open Attachment screen.

SDR 80445
In BlackBerry Enterprise Server Version 4.1 and later, the BlackBerry MDS Services URL does not include the fully-qualified domain name of the computer on which it is installed, so notifications can not be sent to the BlackBerry MDS Services. You can not specify this computer name during the setup program and you can not modify the computer name in the BlackBerry Manager.

SDR 78027
In BlackBerry Enterprise Server Version 4.1 and later, the setup program changed the BlackBerry services to start automatically when installing a service pack or hotfix. If you had previously set the BlackBerry services to start manually, the setup program changed this configuration.

SDR 77476
In BlackBerry Enterprise Server Version 4.1 and later, if you use Add/Remove Programs to update or repair the BlackBerry Enterprise Server, and then open the configuration panel, the Enable Proxy Settings check box on the Proxy Settings tab is no longer selected.

SDR 47779
In BlackBerry Enterprise Server Version 4.1 and later, if you using the BESMigration tool as part of an upgrade, the BESMigration tool does not warn you if you populate the instance names incorrectly.
__________________
In the beginning the Universe was created. This has made a lot of people very angry and is widely regarded as a bad move.

Last edited by jibi : 09-14-2006 at 08:21 AM.
Offline