Join Date: Oct 2004
Location: Jibi's Secret Place
Post Thanks: 0
Thanked 1 Time in 1 Post
If you are installing the BlackBerry Enterprise Server Version 4.1 SP2 on a computer with two or more drives, and you perform the installation on a drive that is not the default drive, the setup program installs a .jks file needed by the BlackBerry MDS Services to accept SSL certificates in the default drive. Errors occur in the BlackBerry Manager when you attempt to administer the BlackBerry MDS Services.
1. Search for the default.jks file in the C:\ drive of the computer where you installed the BlackBerry Enterpriser Server.
2. Copy and paste the file into the following directory:
<Drive>:\<installation directory>\BlackBerry Enterprise Server\MDSS\config\security
If you assign a software configuration to a group and then add a user to that group, the software configuration is not assigned to the new user.
If a user forgets the password for a BlackBerry device on which content protection is turned on, if you reset the userxxx8217;s password remotely, the content-protected BlackBerry device prompts the user to type the BlackBerry device password, which they have forgotten, before they type a new password because content protection uses the password to encrypt the content protection key. You must use the Erase Data and Disable Handheld IT Admin command to remotely erase all user information and application data that the BlackBerry device stores.
Workaround: Do not use the Set a Password and Lock Handheld command to reset the password remotely. If you reset the userxxx8217;s password remotely, the content-protected BlackBerry device prompts the user to type the BlackBerry device password, which they have forgotten, before they type a new password because content protection uses the password to encrypt the content protection key.
If you repeatedly change administrative roles, the connection to the BlackBerry Configuration Database cannot be established and the BlackBerry Manager might shut down.
In BlackBerry Enterprise Server Version 4.1 and later, if you enterprise activate a userxxx8217;s BlackBerry device by connecting the BlackBerry device to the administration computer, each time that you resend service books to the BlackBerry device from the BlackBerry Manager, all PIM data synchronizes to the BlackBerry device and the INVALID_SYNC_STATE error message appears in the BlackBerry Synchronization Service log file.
BlackBerry Attachment Service
In certain circumstances, an error message displays when a user attempts to open an attachment on the BlackBerry device.
Portable Document Format (PDF) attachments do not display layout or characters correctly in the BlackBerry Browser.
In certain circumstances, PDF attachments created with Cognos PDF Server do not render correctly on the BlackBerry device.
In certain circumstances, if a user opens a Microsoft Word attachment on a BlackBerry Connect device, bullet colors do not display correctly.
BlackBerry Collaboration Service
If your instant messaging environment is GroupWise Messenger, you cannot turn off the default setting to show a mobile icon. This feature is only supported on GroupWise Messenger Version 2.x, so if your instant messaging environment contains users on GroupWise Messenger Version 1.x, those users cannot send instant messages from their BlackBerry devices.
Workaround: In the BlackBerry Configuration Database, in the IMConfig table, edit the ShowMobile field using the following
xxx8226; Type 0 to prevent support for showing mobile icons.
xxx8226; Type 1 to permit support for showing mobile icons.
If your instant messaging environment is IBM Lotus Sametime, when a user adds a contact to the Buddy List in their desktop instant messaging program and then starts a conversation with that contact, if the contact receives the invitation on their BlackBerry device the user on the desktop instant messaging program appears to be offline. When the contact joins the conversation on their BlackBerry device, the user on the desktop instant messaging program continues to appear offline until they type the first message of the conversation.
BlackBerry Configuration Panel
In certain circumstances, if you change the path to the folder where the BlackBerry services create log files from a local drive to a network drive, the BlackBerry Configuration Panel completes the process, but the BlackBerry services cannot create logs in the network drive.
Workaround: Specify a local drive as the destination folder for the log files and contact BlackBerry Technical Support.
If an All Points Bulletin (APB) fails, the BlackBerry Dispatcher log file does not display that a failure occurred.
In certain circumstances, if you set up a BlackBerry device during a period of high volume traffic on the BlackBerry Enterprise Server, the BlackBerry Dispatcher remote procedure call (RPC) times out.
BlackBerry Instant Messaging for Microsoft Live Communications Server
If users are using Office Communicator, and they click the Accept&Add menu option on an incoming invitation from a contact that has never been in their contact list before, a xxx8220;setFocusFieldxxx8221; error appears.
If users add themselves to their contact list using their user name and instead of their full email address, then delete themselves, a java exception appears and the user is logged out.
If users are on a server with Public IM Connectivity turned on, and they try to involve Public Instant messaging contacts in a conference, an error message appears.
If users are using Office Communicator and they attempt to add a contact to the contact list before the contact list is fully loaded, an xxx8220;IllegalArgumentExceptionxxx8221; error appears.
Workaround: Upon login, wait until the contact list is loaded completely before attempting to add a contact.
If users block a contact using Office Communicator they can still send messages to that contact and receive messages from that contact.
If users have a contact in the default group, and they select the Remove from Group menu option, a Command Failed error appears.
If users are using Office Communicator on a BlackBerry device, the Remove Contact from Group option does not appear in the menu list.
If a user is on a Live Communications Server Standard Edition, and they are forced from one pool to another, their contact list is automatically deleted by design. The user then receives new add requests for their contacts. If the user clicks the Accept&Add menu option, a uncaught exception appears.
Workaround: Click the Accept menu option and send an add request to your contacts.
If users are using Office Communicator with a BlackBerry 7100 series device, Office Communicator does send or receive typing indicators to or from other BlackBerry devices.
In some circumstances, users are unable to load Office Communicator using a BlackBerry browser.
If users attempt to log in to Microsoft Windows Messenger using serial bypass, a xxx8220;message queue overflowxxx8221; error message might appear.
If users are using Office Communicator on a BlackBerry 7100 device, and they search for a contact in the contact list, the contact list does not snap to already known contacts.
If users include a space character in their Microsoft Windows passwords, they are unable to log in to Windows Messenger or Office Communicator. An error message appears.
If a user does not have permission to access Office Communicator and they attempt to log in, a xxx8220;!xxx8221; error message appears.
If users are using Windows Messenger, and they copy a conversation history into an Enterprise Messenger conversation, an xxx8220;ArrayIndexOutOfBoundsxxx8221; error message appears.
If users are using Windows Messenger and they delete a contact, a xxx8220;message queue overflowxxx8221; error message might appear and they are signed out of Enterprise Messenger.
BlackBerry Instant Messaging for Novell GroupWise
If users try to move a contact that is already in all folders in the contact list, a xxx8220;Command Failedxxx8221; error appears.
If the BlackBerry Collaboration Service is stopped after users log in to GroupWise Messenger, users might be logged out of GroupWise Messenger and an error message containing the user's user name and an exclamation mark might appear.
If users have a contact in multiple folders, and they ignore that contact in one folder, that contact is not ignored in other folders.
If users attempt to ignore the contact in other folders, a xxx8220;Command Failedxxx8221; error appears.
If users try to send a message to a contact who is ignored in one folder and unignored in another, the message is not delivered.
If users browse to their address book to add a contact using the contactxxx8217;s email address, once the user clicks OK on the Add User dialog box, a Command Failed error appears.
If a user sends an instant message to a contact and then invites that same contact to a conference, if the contact accepts the conference using GroupWise Messenger on their computer, two GroupWise Messenger conversations are open.
If users delete a contact that appears in multiple groups, that contact is only deleted in the group from which they deleted it. If the contact appears in other groups, users cannot modify or delete that contact. Users cannot send an instant message to that contact unless that contact sends a message to them first.
If users try to edit the default GroupWise folder, a xxx8220;Command Failedxxx8221; error message appears.
If users sends a URL in an Enterprise Messenger conversation, and their contact is using Enterprise Messenger on their BlackBerry device, the contact receives the URL with a smiley icon in it.
BlackBerry Instant Messaging for Sametime
If the BlackBerry MDS Connection Service and the BlackBerry Collaboration Service are disabled on the BlackBerry Enterprise Server, users who were online when the services were disabled are not notified that they are no longer connected.
The xxx8220;<Start Typing Here>xxx8221; message that appears in the text entry field might not disappear when users start typing in that field.
If users have a large contact list, when they log on to their account using their BlackBerry device, highlight a group, and select the Add Person menu option while the contact list is loading, an illegal argument exception. appears
If a user creates two groups with the same name that differ only by capitalization on their desktop computer, and add at least one contact to each group, then log into the same account on their handheld client, highlight the first group in the contact list and select Add Person from the menu, an illegal argument exception appears.
If a single chat between a BlackBerry device user and a desktop computer user is initiated by the device user and the desktop user invites other participants to the existing chat window, then the device that originated the single chat will receive an invitation instead of having the single chat window on the device converted to a meeting.
If you create an IT policy that contains a VoIP Emergency Number that begins with a zero, the BlackBerry Manager removes the zero from the number.
After you upgrade your BlackBerry Enterprise Server to Version 4.1SP2, if you create a new IT policy by copying an IT policy that existed prior to the upgrade, the copied IT policy does not contain the settings of the original.
If you are administering a BlackBerry Enterprise Server Version 4.0.x using either the BlackBerry Manager Version 4.1 SP2 or the BlackBerry Manager for MMC Version 4.1 SP2 on another BlackBerry Enterprise Server in the same BlackBerry Domain, you cannot create global message redirection filters on the BlackBerry Enterprise Server Version 4.0.x.
Workaround: Use the BlackBerry Manager for MMC Version 4.0.x to create or edit global filters.
If you are using a BlackBerry Manager at Version 4.1 SP2 to administer a BlackBerry Enterprise Server at Version 4.1 or Version 4.1 SP1, you should not have the option to create a one-to-many relationship between that BlackBerry Enterprise Server and a BlackBerry Collaboration Service. This feature is supported only if all BlackBerry components are Version 4.1 SP2.
In the BlackBerry Manager role mapping XML file (extracted from bbmgrw32.exe), in the BlackBerry Collaboration Service Properties node, the <localaccess> element lists the incorrect Name attribute (xxx8220;Local Access Controlxxx8221;). The Name attribute should be xxx8220;Access Controlxxx8221;.
Workaround: In the XML file, manually change the Name attribute in <localaccess type=xxx8220;propNodexxx8221; Name=xxx8220;Local Access Controlxxx8221;/> to xxx8220;Access Controlxxx8221;.
If you set user filters for a user account in the BlackBerry Manager or on a BlackBerry device, and then set the enterprise activation password for the same user account, the filters are deleted in the BlackBerry Manager and on the BlackBerry device.
The BlackBerry Manager does not correctly indicate the PGP Security Capabilities for a userxxx8217;s BlackBerry device in the user Properties when the user is enabled for PGP.
In BlackBerry Enterprise Server Version 4.1 and later, in the following situation, access mapping rules are lost for user accounts; the push rules window does not open.
- You assigned access roles to BlackBerry device users.
- You created a group and assigned those BlackBerry Device users to it.
- You added additional access rules to the group.
The BlackBerry Manager is not compatible with Microsoft .NET Framework 2.0.
BlackBerry MDS Services
If you are upgrading your BlackBerry environment from Version 4.1 and later to Version 4.1 SP2, and you add a new instance of BlackBerry MDS Connection Service created at Version 4.1SP2, the BlackBerry MDS Services adds this instance to the list of available BlackBerry MDS Connection Services. If you do not intend to use this instance and manually stop the service, the BlackBerry MDS Services retains the instance on its list of available BlackBerry MDS Connection Services. When activating BlackBerry MDS Runtime on BlackBerry devices, if the BlackBerry MDS Services attempt to connect to the stopped instance of the BlackBerry MDS Connection Service, the activation fails.
If you have a stopped instance of the BlackBerry MDS Connection Service in your BlackBerry environment, manually remove this instance from the BlackBerry MDS Connection Service Definition list of the BlackBerry MDS Services.
After you removed a user account from the BlackBerry Enterprise Server, the userxxx8217;s BlackBerry device is not removed from the BlackBerry MDS Application Repository.
The BlackBerry MDS Application Repository server logs the content of secure messages when running in DEBUG mode.
BlackBerry Messaging Agent
In BlackBerry Enterprise Server Version 4.1 and later, if a user receives a message signed with S/MIME in which the message starts with a SPACE or TAB character, the BlackBerry Messaging Agent removes the message body when reconciling to the userxxx8217;s BlackBerry device.
In BlackBerry Enterprise Server Version 4.1 and later, if a userxxx8217;s BlackBerry device is running BlackBerry Device Software Version 4.0 and is not enabled for S/MIME support, the BlackBerry Messaging Agent does not forward encrypted messages to the userxxx8217;s BlackBerry device.
When a user changes Server Relay Protocol identifiers to an invalid value and then changes it back to a valid value, the service books do not update correctly.
BlackBerry Policy Service
If you add a user to the BlackBerry Enterprise Server and then delete that user, the Delete On option (in Messages Options > Email Reconciliation) on the BlackBerry device is set to Handheld for all existing users because the BlackBerry Policy Service sends out a service book update to all existing users when the user is deleted.
If you set the Allow Other Message Services IT policy rule to True, the BlackBerry device does not allow other message services.
BlackBerry Synchronization Service
If a user creates a contact in Microsoft Outlook that does not contain a name or company name, the BlackBerry Synchronization Service does not synchronize the contact to the userxxx8217;s BlackBerry device. If a user is performing an enterprise activation using the BlackBerry Desktop Manager (for example, after upgrading their BlackBerry Device Software) an 'Unable to write or update application data' error occurs and the contact is not synchronized.
Workaround: Include either company or name data in all contacts.
If you upgrade to BlackBerry Enterprise Server Version 4.1 SP2 and a user adds a picture to an address book contact from their BlackBerry device running BlackBerry Device Software Version 4.2, the picture does not synchronize to the desktop email program.
Workaround: When upgrading the BlackBerry Enterprise Server, manually reset Reset PIM Sync Global Mapping to
synchronize the Picture field.
In certain circumstances, enterprise activation might not complete if the delivery status of the initialization verification packet is received by the BlackBerry device subsequent to a new BlackBerry device request.
In certain circumstances, you cannot stop the BlackBerry Synchronization Service.
Workaround: Use the task manager to stop the BlackBerry Synchronization Service.
The BlackBerry Synchronization Service log file does not log all events.
The BlackBerry Synchronization Service and BlackBerry Synchronization Connector log files do not have a description for event ID .
If conflict resolution for the BlackBerry Enterprise Server is set to Device Wins and wireless synchronization is turned off, filter updates on the BlackBerry device are not synchronized to BlackBerry Manager.
If you create a new filter, delete a filter, and then move a filter from a BlackBerry device within a short period of time, the BlackBerry Synchronization Service reverts the changes.
When creating a contact on the BlackBerry device, if a user modifies the name format preferences, the changes are not synchronized to the desktop email program.
If you are installing the BlackBerry Enterprise Server Version 4.1 SP2, and you select Ukraine as your country, the setup program automatically populates the SRP connection with incorrect information.
1. In the Host field, delete srp.uk.blackberry.net.
2. Type srp.ua.blackberry.net
3. Continue with the installation process.
When you upgrade from BlackBerry Enterprise Server Version 4.1 and later to BlackBerry Enterprise Server Version 4.1 SP2, and during the upgrade you add support for instant messaging, the setup program does not remove the placeholder record in the IMConfig table when it adds the new record listing the computer where you installed the BlackBerry Collaboration Service. As a result, when you view the IM to BES Mappings list in the BlackBerry Manager, you see the invalid computer name xxx8220;IM-1xxx8221;.
Workaround: Do not select the invalid computer name when mapping instances of your BlackBerry Enterprise Servers to a BlackBerry Collaboration Service.
In certain circumstances, when you install the BlackBerry Enterprise Server Version 4.1 and later, if you specify a network path as the destination folder for the log files, the installation process completes but the BlackBerry services cannot create logs in the network drive.
Workaround: After you complete the setup program, confirm that your log files appear on the network drive. If not, use the BlackBerry Configuration Panel to specify a local drive as the destination folder for the log files and contact BlackBerry Technical Support.
If your database environment is Microsoft SQL Server 2005, the setup program does not change the authentication mode to Mixed Mode when the user requests the change. The setup program creates the BlackBerry Configuration Database, but cannot create the BlackBerry MDS Services databases, and the xxx8220;DB upgrade failed. Database connection attempt failedxxx8221; error occurs.
Workaround: You must change your database server to Mixed Mode before starting the setup program. See the BlackBerry Enterprise Server Installation Guide for more information about database environment settings required by the BlackBerry Enterprise Server.
Wireless calendar synchronization
If a meeting organizer sent a meeting invitation to a large number of individual invitees, this might cause high CPU usage and the BlackBerry Enterprise Server might stop responding.
If your messaging environment is Microsoft Exchange 5.5, when a meeting attendee accepts an invitation to a recurring yearly meeting, the meeting details do not synchronize correctly to the attendeexxx8217;s BlackBerry device.
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-12-2006 at 11:44 PM.