BES 5 0 1 Technical Note En

8/3/2019 BES 5 0 1 Technical Note En

http://slidepdf.com/reader/full/bes-5-0-1-technical-note-en 1/20

BlackBerry Enterprise Server 5.0 SP1

BlackBerry Enterprise ServerVersion 5.0 Service Pack 1

Technical Note for JapaneseEnvironments






1

Table of Contents

Overview ........................................................................................................................................... 3 Related resources ..................................................................... ............................................................... .... 3

Language support matrix .................................................................................................................. 3 Installation requirements .................................................................................................................. 4 Certified environments ...................................................................................................................... 4 Tested and recommended environments ......................................................................................... 5

Tested and recommended environments for BlackBerry Enterprise Server 5.0 SP1 with MicrosoftExchange 2007 (Japanese) ....................................................................................... .................................. 5 Tested and recommended environments for BlackBerry Enterprise Server 5.0 SP1 with IBM LotusDomino 8.5 (Japanese) ......................................................................................................... ....................... 5 Environment changes from previous releases ........................................................... .................................. 6

Language options and selections ..................................................................................................... 6 Installing BlackBerry Enterprise Server 5.0 SP1 for Microsoft Exchange ........................................ 7 Installing BlackBerry Enterprise Server 5.0 SP1 for IBM Lotus Domino .......................................... 7 Upgrading to BlackBerry Enterprise Server 5.0 SP1 for Microsoft Exchange.................................. 7 Upgrading to BlackBerry Enterprise Server 5.0 SP1 for IBM Lotus Domino .................................... 7 Postinstallation tasks for Japanese environments ........................................................................... 8

Install the East Asian Language code page for Windows operating systems .......................................... .... 8 Add the MAPI encoding value to the registry (Microsoft Exchange environments only)............................... 8 Install the kochi-mincho.ttf TrueType font file ............................................................. .................................. 8 Configure Unicode support in calendars in a Microsoft Exchange environment .......................................... 9

Prerequisites for HTML email support on BlackBerry devices ....................................................... 10 Shift-JIS support ............................................................................................................................. 10 Microsoft Office file attachment support ......................................................................................... 10 Using the BlackBerry Enterprise Server Trait Tool in a Microsoft Exchange environment ............ 10 Limitations in a Japanese environment .......................................................................................... 10

Limitations for IT policies ............................................................ ................................................................ 10 Limitations for contact list lookups................................................................... ........................................... 11

Fixed issues in BlackBerry Enterprise Server 5.0 SP1 .................................................................. 12 ............................................................. ................................................................. ..................... 12

...................................................... ................................................................. .......... 13

...................................................... ................................................................. .......... 13 Known issues for BlackBerry Enterprise Server 5.0 SP1 ............................................................... 14

BlackBerry Attachment Service ............................................................. ..................................................... 14 BlackBerry Administration Service ........................................................ ..................................................... 14 BlackBerry Enterprise Server ................................................................ ..................................................... 15 BlackBerry Configuration Database ................................................................................................ ........... 15 BlackBerry Desktop Manager ........ ................................................................. ........................................... 15 IT policy ..................................................... ................................................................. ................................ 15 Japanese localization ...................................................... ................................................................. .......... 15 Setup application.................................................. ................................................................. ..................... 15



Technical Note for Japanese Environments

2

Wireless calendar synchronization ........................................................................................................... .. 16 Legal notice .................................................................................................................................... 17




3

Overview

This document provides information about installing or upgrading to BlackBerry® EnterpriseServer 5.0 SP1 in a Japanese environment. It includes following information:

environments that are certified for BlackBerry Enterprise Server 5.0 SP1

tasks required to upgrade from BlackBerry Enterprise Server 4.1 SP4 Japanese to 5.0SP1 Japanese

known issues in previous versions of the BlackBerry Enterprise Server that have beenresolved, and known issues that exist in BlackBerry Enterprise Server 5.0 SP1

This document focuses on issues specific to a Japanese BlackBerry Enterprise Serverenvironment and supersedes all other documentation that is issued as part of the BlackBerryEnterprise Server 5.0 SP1 documentation package. For detailed information about how toinstall and manage the BlackBerry Enterprise Server, see the BlackBerry Enterprise Server5.0 SP1 documentation.

Related resources

BlackBerry Enterprise Server Installation Guide system requirements

instructions for new installations

BlackBerry Enterprise Server Feature and Technical Overview

BlackBerry Enterprise Server features

system architecture

data and process flows

BlackBerry Enterprise Server Administration Guide system setup and management

BlackBerry device implementation instructions

“Activation of Yomi field synchronization afterBlackBerry Enterprise Server upgrade” (KB13854)

manual synchronization of the Yomi fieldmappings between the BlackBerry device andthe messaging server

Supported Teminology documentation (TBD) new definitions for RIM certified and supportedenvironments

Errata differences between the Japanese terms usedin the product and in the BlackBerry EnterpriseServer 5.0 SP1 documentation

Language support matrix

BlackBerry Enterprise Server 5.0 SP1 supports both English and Japanese environments. Formore information, see the Installation requirements section.






5

Tested and recommended environments

In tested environments, documented configurations have undergone validation andacceptance testing to determine the compatibility of the BlackBerry Enterprise Server. Duringthis testing, RIM internally identified and addressed any high-impact issues. Performancetesting has been assumed in general from testing in English environments.

Tested and recommended environments for BlackBerry Enterprise Server 5.0SP1 with Microsoft Exchange 2007 (Japanese)

Item Requirement Version

Microsoft® Exchange operating system ofhost computer

As required by Microsoft

messaging serversoftware

Microsoft® Exchange Server 2003 SP2 (32-bit)(Japanese)

Microsoft® Exchange Server 2007 SP1 (64-bit)(Japanese)

BlackBerry Enterprise

Server

operating system of

host computer

Windows Server® 2003 SP2 (32-bit) (Japanese)

Windows Server 2003 R2 SP2 (32-bit)(Japanese)


Windows Server 2008 SP2 (64-bit) (Japanese)

BlackBerryConfiguration Database

operating system ofhost computer





database server Microsoft® SQL Server® 2005 (32-bit)(Japanese)

Microsoft SQL Server 2005 SP3 (32-bit)(Japanese)

Microsoft SQL Server 2008 (64-bit) (Japanese)

Microsoft SQL Server 2005 Express SP3 (32-bit)(Japanese)

Tested and recommended environments for BlackBerry Enterprise Server 5.0SP1 with IBM Lotus Domino 8.5 (Japanese)

Item Requirement Version

IBM® Lotus® Domino® operating system ofhost computer

As required by IBM

messaging serversoftware

IBM Lotus Domino version 8.5 (32-bit)(Japanese Language Pack)

IBM Lotus Domino version 7.0.3 (32-bit)(Japanese Language Pack)

IBM Lotus Domino version 8.0.2 (32-bit)(Japanese Language Pack) and with LotusDomino Hotfix HNAA7FBED6 and MK1A7FCGR8

BlackBerry EnterpriseServer




Windows Server® 2003 R2 SP2 (64-bit)(Japanese)

Windows Server 2003 R2 SP2 (32-bit)

(Japanese)Windows Server 2008 SP2 (32-bit) (Japanese)




6

BlackBerryConfiguration Database






Windows Server 2008 SP2 (64-bit) (Japanese)database server Microsoft® SQL Server® 2005 SP3 (32-bit)

(Japanese)

Microsoft SQL Server 2005 SP3 (64-bit)(Japanese)



Microsoft SQL Server 2005 Express SP3 (32-bit)(Japanese)

Environment changes from previous releases

For BlackBerry Enterprise Server 5.0 SP1, the certified database is Microsoft SQL

Server 2005 Express Edition. In April 2008, Microsoft stopped Mainstream Support of MSDE, but offers Extended

Support until April 2013.

RIM will announce supported requirements for Microsoft Exchange 2010 shortly afterthe public release of Microsoft Exchange 2010 by Microsoft.

Third-party software installation on various Windows operating systems is subject toany limitations and requirements that Microsoft or IBM indicates.

Language options and selections

The language options for installation and server configuration are as follows:

If you install the BlackBerry Enterprise Server on a Japanese Windows operating system,the setup application and the BlackBerry Configuration Panel is localized in Japanese.

If you install the BlackBerry Enterprise Server on an English Windows operating system,the setup application and BlackBerry Configuration Panel is localized in English.

If you install the BlackBerry Enterprise Server on an operating system that is in alanguage other than Japanese, the setup application and BlackBerry Configuration Panelis localized in English.

The language options when administering the BlackBerry Enterprise Server using theBlackBerry Administration Service are as follows:

When logging into the BlackBerry Administration Server, the administrator can select alanguage.

To change the language option, the administrator must log out, select the new languageand then log back in to the BlackBerry Administration Server.




7

Installing BlackBerry Enterprise Server 5.0 SP1 for MicrosoftExchange

If this is a new installation of the BlackBerry Enterprise Server, see the BlackBerry Enterprise Server for Microsoft Exchange Installation and Configuration Guide for planning,

prerequisites, and installation information.

Once the installation is complete, see the Postinstallation tasks for Japanese environments section to complete any configuration tasks that are required by your organization’senvironment.

Installing BlackBerry Enterprise Server 5.0 SP1 for IBM LotusDomino

If this is a new installation of the BlackBerry Enterprise Server, see the BlackBerry Enterprise Server for IBM Lotus Domino Installation and Configuration Guide for planning, prerequisites,and installation information.

Once the installation is complete, see the Postinstallation tasks for Japanese environments section to complete any configuration tasks that are required by your organization’senvironment.

Upgrading to BlackBerry Enterprise Server 5.0 SP1 for MicrosoftExchange

If you are upgrading the BlackBerry Enterprise Server, see the BlackBerry Enterprise Server for Microsoft Exchange Upgrade Guide for planning, prerequisites, and installationinformation.

1. Log in to the computer that hosts the BlackBerry Enterprise Server using the besadminservice account.

2. Double-click the BESX_Upgrader.zip file.

3. Extract the setup application files to a local drive on the computer.

4. Browse to the location of the setup application files.

5. Double-click setup.exe.

6. Click Update.

7. Complete the configuration screens.

8. Click Finish.

Once the upgrade process is complete, see the Postinstallation tasks for Japaneseenvironments section to complete any configuration tasks that are required by your

organization’s environment.

Upgrading to BlackBerry Enterprise Server 5.0 SP1 for IBM LotusDomino

If you are upgrading the BlackBerry Enterprise Server, see the BlackBerry Enterprise Server for IBM Lotus Domino Upgrade Guide for planning, prerequisites, and installation information.

1. Log in to the computer that hosts the BlackBerry Enterprise Server using anadministrative account with appropriate database permissions.

2. Change the startup type of the IBM Lotus Domino server to manual.

3. Stop the IBM Lotus Domino server.

4. Double-click the BESD_Upgrader.zip file.




8

5. Extract the setup application files to a local drive on your computer.

6. Browse to the location of the setup application files.

7. Double-click setup.exe.

8. Click Update.

9. Complete the configuration screens.

10. Click Finish.

Once the upgrade process is complete, see the Postinstallation tasks for Japaneseenvironments section to complete any configuration tasks that apply to your organization’senvironment.

Postinstallation tasks for Japanese environments

After you install BlackBerry Enterprise Server 5.0 SP1 or upgrade to it, you must review andcomplete any of the following tasks that apply to your organization’s environment:

install the East Asian Language code page for Windows operating systems

add the MAPI encoding value to the registry (Microsoft Exchange environments only)

install the kochi-mincho.ttf True Type font file

Configure Unicode support in calendars (Microsoft Exchange environments only)

Install the East Asian Language code page for Windows operating systems

Complete this task if the computer that hosts the BlackBerry Attachment Service has anEnglish Windows operating system.

1. On the computer that hosts the BlackBerry Attachment Service, click Start >Control Panel > Regional and Language Options .

2. On the Languages tab, select the Install files for East Asian languages check box.

3. Click OK.

Add the MAPI encoding value to the registry (Microsoft Exchangeenvironments only)

1. On the computer that hosts the BlackBerry Attachment Service, click Start > Run.

2. Type regedit.

3. Click OK.

4. Navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Research In Motion\BlackBerryEnterprise Server\Agents.

5. Right-click Agents.

6. Click New > DWORD Value.

7. Create a DWORD value named MAPIEncoding.

8. Set the Value data to 1.

9. Click OK.

10. Close the Registry Editor.

Install the kochi-mincho.ttf TrueType font file

You must complete this task so that BlackBerry Attachment Service 4.1 SP6 can correctly

render a .pdf file in Japanese. Previous versions of the BlackBerry Enterprise Server do notsupport the rendering of .pdf files in Japanese.




9

Before you begin:

Download the kochi-mincho.ttf TrueType® font file and install it on the computerthat hosts the BlackBerry Attachment Service.

Verify that you meet all licensing requirements to download and use this font file.

1. Visit http://ftp.debian.org/debian/pool/main/t or another font supplier to download thettf-kochi font file.

2. Unzip the ttf-kochi_1.0.20030809.orig.tar.gz file.

Configure Unicode support in calendars in a Microsoft Exchange environment

Install the required Microsoft hotfixes in a Microsoft Exchange 2003 environment

1. If you use Unicode text in calendars, install the following two hotfixes:

Visit http://support.microsoft.com/kb/913643 to download and install the requiredhotfix KB 913643 on the messaging server.

Visit http://support.microsoft.com/kb/923537 to download and install the required

hotfix KB 923537 on the computer that will host the BlackBerry Enterprise Server.2. Install BlackBerry Enterprise Server 5.0 SP1. See the BlackBerry Enterprise Server

for Microsoft Exchange Installation and Configuration Guide .

Configure the BlackBerry Enterprise Server to support Unicode text in calendars in aMicrosoft Exchange environment

If you are using Microsoft Exchange and use Unicode text in calendars, you may encounteran issue where an appointment message box shows question marks and boxes rather thanthe expected Japanese text. You must complete this task for all Microsoft Exchange versionsto ensure calendar items modified using CDO retain the proper characters in fields such assubject, location, or notes.

1. On the computer that hosts the BlackBerry Enterprise Server, click Start > Run.

2. Type regedit.

3. Click OK.

4. In the left pane, navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Research InMotion\BlackBerry Enterprise Server\Agents.

5. Right-click Agents.

6. Click New > DWORD Value.

7. Create a DWORD value named SetLocaleIDs.

8. Set the Value data to 1.

9. Click OK.

10. Close the Registry Editor.

11. In the Windows Services, restart the BlackBerry Messaging Agent.

For more information, visit www.blackberry.com/support to read KB14757 “Japanesecharacters do not display correctly in the calendar items for BlackBerry Smartphone users”.

Once you configure the SetLocaleIDs registry key, you may then encounter that, in calendarappointments, the names of the invitees are changed from the display name to the username.This is due to a limitation in the Unicode handling capability of the Microsoft CDO.DLL file. Formore information, visit www.blackberry.com/support to read KB19497 “Meetings invite forBlackBerry smartphone users show Invitees Username rather than Display Name”.

http://www.blackberry.com/support










10

Using Microsoft Exchange Web Services in a Microsoft Exchange 2007 environment

If you are running the BlackBerry Enterprise Server 5.0 SP1 in an environment that includesusers on Microsoft Exchange 2007 SP1 or later only, you can configure the calendar to usethe Microsoft Exchange Web Services interface which corrects the issues described inKB14757 and KB19494 on www.blackberry.com/support.

The Microsoft Exchange Web Services does not use MAPI and CDO libraries. MAPI andCDO libraries are part of Microsoft Exchange 2003 and are currently end of life with Microsoft.Microsoft offers Extended Support only for MAPI and CDO libraries.

Except for managing calendars, all other functions of the BlackBerry Enterprise Server stilluse MAPI profiles.

To configure the BlackBerry Enterprise Server to use Microsoft Exchange Web Services, seethe Managing Calendars chapter in the BlackBerry Enterprise Server Administration Guide .

Prerequisites for HTML email support on BlackBerry devices

To support HTML email on BlackBerry devices, you must use BlackBerry Enterprise Server4.1 SP6 or later and BlackBerry Device Software 4.5 or later. Previous versions of the

BlackBerry Enterprise Server do not support HTML email on the BlackBerry device.

If you use the BlackBerry Enterprise Server on an English Windows operating system, installthe extra language support on the computer by completing the task Install the East AsianLanguage code page for Windows operating systems from the Postinstallation tasks forJapanese environments section.

Shift-JIS support

The BlackBerry Enterprise Server 4.1 SP6 and later support file attachments in .rtf and .txtformats that are encoded in Shift-JIS.

Microsoft Office file attachment supportBlackBerry Enterprise Server 4.1 SP6 and later support Microsoft® Office 2007 fileattachments (for example, .docx files, .xlsx files, and .pptx files). Users cannot view charts inMicrosoft Office 2007 attachments on BlackBerry devices.

Using the BlackBerry Enterprise Server Trait Tool in a MicrosoftExchange environment

You can use the BlackBerry Enterprise Server Trait Tool in Japanese environments andoperating systems. The BlackBerry Enterprise Server Trait Tool is English-only, and onlyaccepts commands, command line options, and characters in the English language.

Limitations in a Japanese environment

When you run the BlackBerry Enterprise Server in a Japanese environment, the followinglimitations exist:

limitations for IT policies

limitations for contact list lookups

limitations for the BlackBerry Attachment Service

Limitations for IT policies

IT policy rules and Wi-Fi configuration settings that accept string values do not support

Unicode text. If you attempt to submit an IT policy that contains Japanese characters, youreceive an error message similar to the following:








11

<Policy Name> contains an invalid entry. Unicode strings are not supported for this field.Please use Latin characters only.

You can only use Latin characters in the corresponding IT policy.

For more information about IT policy rules, see the BlackBerry Enterprise Server Policy Reference Guide .

Limitations for contact list lookups

The BlackBerry Enterprise Server does not support contact list lookups that use Yomiaddress fields. Users cannot look up contacts using the phonetic Yomi reading for addressbook fields. This limitation affects the following tasks:

adding contacts to contact lists on BlackBerry devices

looking up contacts when sending messages on BlackBerry devices

looking up invitees when creating meetings on BlackBerry devices

At time of publication, this limitation exists because Microsoft Exchange and IBM LotusDomino do not currently support Yomi fields in the user directory. RIM is investigating whether

Microsoft Exchange and IBM Lotus Domino will support Yomi field lookups in a future release.

Yomi fields have been added to the contact list for BlackBerry devices in BlackBerry® DeviceSoftware version 4.2.2 and higher. These fields synchronize with the BlackBerry device andthe messaging server when using BlackBerry Enterprise Server 4.1 SP4J or later.




12

Fixed issues in BlackBerry Enterprise Server 5.0 SP1

SDR 128659 One dialog box in the setup application for Japanese was not translated.

SDR 169257,SDR 179376

You could not activate BlackBerry® Connect™ 4.0 devices.

SDR 154740 In BlackBerry Enterprise Server for Microsoft Exchange, picture attachments fromDoCoMo FOMA handsets could not be viewed on the BlackBerry device.

This problem occured when an email message contained no text and a messageattachment. In this scenario, at the Microsoft Exchange server level, software thatappended the confidentiality notice, as used by RIM, converted the attachment to anembedded message (when there is no text in the message body). The imagebecame a second level attachment. Currently, the BlackBerry device does notsupport second level attachments.

This issue is fixed in the BlackBerry Enterprise Server 5.0 for Microsoft Exchange.In BlackBerry Enterprise Server for Microsoft Exchange, users could not view

picture attachments from DoCoMo FOMA.SDR 176719 In the setup application, the SRP Address > Test Result screen contained English

text.

SDR 182740 The BlackBerry Monitoring Service did not display the active users on theBlackBerry Enterprise Server 4.1 SP6 for Microsoft Exchange.

SDR 183057 In the BlackBerry Enterprise Server for IBM Lotus Domino, SMIME Japanesecharacters in the body text of encrypted messages and in the file name ofattachments received on the BlackBerry device do not render correctly.

SDR 185328 Some attached files in .rtf format did not display correctly on the BlackBerry device.

SDR 203565 The BlackBerry Attachment Service could not render Japanese .xpdf attachments.

SDR 205547 When you searched for BlackBerry Device Software bundles in the Japanese

BlackBerry Administration Service, the BlackBerry Administration Service returnednothing.

SDR 206470 In the BlackBerry Enterprise Server for Microsoft Exchange, when you savedchanges to an Email server instance, the BlackBerry Administration Servicedisplayed the following error message: “A connection could not be made using theSRP data provided. Please verify and save the entries”.

SDR 207355 In the BlackBerry Enterprise Server for Microsoft Exchange, when you stopped orrestarted a BlackBerry Policy Service using the BlackBerry Administration Service,the BlackBerry Policy Service did not stop and the BlackBerry AdministrationService displayed the following error message:“Impossible to finish the request.”

SDR 208018 BlackBerry database notification system notifications were not triggered by users

that did not have db_owner permissions on the BlackBerry Configuration Database.SDR 248598 In BlackBerry Enterprise Server 4.1 SP6 for Domino, the BlackBerry Manager

required a non ISO format to represent the Japanese locale (jp_JA instead of ja_JP)when importing IT policies.

In BlackBerry Enterprise Server 4.1 SP6 MR3 and later, this issue is resolved.

SDR 270737 In a Microsoft Exchange 2007 environment, if a user updated a calendarappointment from the BlackBerry device that contained Unicode (Japanese)characters in the subject, location, or message body fields, and sent the update tothe meeting participants, the Japanese characters did not appear correctly (shownas question marks) when recipients viewed the updated calendar appointment inMicrosoft Outlook.

SDR 303538 If you installed the BlackBerry Monitoring Service on a computer with a Japaneseoperating system, notification messages displayed in Japanese in the BlackBerryMonitoring Service, but the notification message body did not display correctly whenit was received in the mailbox on the recipient’s computer and on the BlackBerry




13

device.

SDR 337340 If a user created an email that did not contain Japanese characters and attached anattachment with a Japanese filename on a BlackBerry device, the recipient receivedthe attachment as a corrupted file.

SDR 337456 In the Attachment Server tab in the BlackBerry Configuration Panel, if you tried toconvert a file with a filename that included Japanese characters, the BlackBerryConfiguration Panel displayed an English message and corrupted Japanesecharacters.

The issue was resolved in SDR 180658.

SDR 360362 After you remove a standby BlackBerry® Enterprise Server instance, the BlackBerryAdministration Service 5.0 continued to display some of the standby BlackBerryEnterprise Server components in the Components view.

In BlackBerry Enterprise Server 5.0 SP1, after you remove a standby BlackBerryEnterprise Server, the BlackBerry Administration Service could successfully removethe components.

SDR 370318 When you upgraded a BlackBerry Enterprise Server from 4.1 SP6 to 5.0 SP1, thesetup application did not prompt you to remove the BlackBerry Enterprise Server 4.1SP6 software.

SDR 133621 In a BlackBerry Enterprise Server for Microsoft Exchange environment, if a usersends a message with Japanese text that is longer than 16,000 bytes from aBlackBerry device, the text displays correctly on the recipient’s Microsoft® Outlook®client. Any text beyond 16,000 bytes is truncated on the recipient’s BlackBerrydevice.

For more information, visit www.blackberry.com/support to read KB03727.

SDR 134562 In a BlackBerry Enterprise Server for Microsoft Exchange environment, addressbook entries created in Microsoft Outlook that contain double-byte alphanumericcharacters or spaces might not synchronize correctly to the contact list on theBlackBerry device.

SDR 332840 When you apply the External Domain application control policy to an application onBlackBerry devices, the application can access other domains.

If only external connections are being made from the BlackBerry device, you do notneed to specify internal restrictions. The BlackBerry device can automaticallyattempt to use an internal connection if possible, especially if the BlackBerry deviceis activated on a BlackBerry Enterprise Server. You must specify both internal andexternal restrictions to properly restrict connections to web sites.

SDR 132809 In a BlackBerry Enterprise Server for Microsoft Exchange environment, Japanesecharacters do not display correctly in the memo field of the calendar on theBlackBerry device.

Workaround:

1. Apply Microsoft hotfixes KB913643 and KB923537. These hotfixes fix a CDOissue that prevents the Unicode calendar from working correctly. Without thesehotfixes, the Microsoft Exchange Server 2003 might stop responding.

2. Add a registry value to turn on Unicode text support in calendars.

SDR 143513 In certain circumstances, when you upgrade to BlackBerry Enterprise Server 5.0SP1, wireless synchronization options might not be rendered on the BlackBerrydevice, and a user cannot synchronize the address book, tasks, or memo padwirelessly.

Workaround:

Deleting and undeleting the sync service books corrects this issue. Wirelesssynchronization options appear and wireless synchronization is possible for bothmemos and tasks.

1. On the BlackBerry device, in the device options, click Advanced Options.2. Click Service Books.








14

3. Highlight the SYNC service book.

4. Press Menu.

5. Click Delete.

6. When the confirmation message displays, click Delete.

7. Wait for approximately 30 seconds.

8. Press Menu.9. Click Undelete.

SDR 176144 In BlackBerry Enterprise Server for Microsoft Exchange, a half-sized katakanacharacter in the subject line of a message becomes full-sized when viewed on theBlackBerry device and in Microsoft Outlook.

Workaround: When sending the emails, a user must have selected theInternational Option - "Auto select encoding for outgoing messages feature".Microsoft Outlook 2007 would have chosen ISO-2022-JP and the halfwidthkatakana converted to full width. Turn off the auto-selection and sending emails.

SDR 249701 If you install a BlackBerry Enterprise Server on the same computer as theBlackBerry Collaboration Service, and then you install another instance of theBlackBerry Collaboration Service on the same computer without starting the firstBlackBerry Collaboration Service instance, the second BlackBerry Collaboration

Service instance overwrites the information of the first BlackBerry CollaborationService instance in the BlackBerry Configuration Database.

Workaround: Start the initial BlackBerry Collaboration Service instance before youinstall subsequent BlackBerry Collaboration Service instances on the samecomputer.

Known issues for BlackBerry Enterprise Server 5.0 SP1

This section lists the known issues for BlackBerry Enterprise Server 5.0 SP1 for MicrosoftExchange and BlackBerry Enterprise Server 5.0 SP1 for IBM Lotus Domino.

BlackBerry Attachment Service

SDR 99449 Users cannot view the following images in message attachments on the BlackBerrydevice:

embedded Microsoft Office WordArt images

vector images in .doc file attachments, including grouped text boxes and images,which are treated as vector images

graphs and cell formatting in .xls file attachments

SDR 102839,

SDR 104544

When a user extracts the contents of a .zip file that contains files in Japanese, the filenames do not display correctly on the BlackBerry device.

On NT-based systems such as Windows NT, Windows 2000, and Windows XP, fileand folder names are stored as Unicode. Such files and folders can only beprocessed by Unicode-aware applications. WinZip is not a Unicode-awareapplication. WinZip can only display and process characters that exist in your currentcodepage.

SDR 134713 When a user tries to view a file using the BlackBerry® Browser, embedded items inthe file, such as tables, text boxes, figures, and pictures might not downloadcorrectly.

BlackBerry Administration Service

SDR 145389 In BlackBerry Enterprise Server for Microsoft Exchange, a Japanese Vcardattachment created on the BlackBerry device is not rendered correctly in MicrosoftOutlook.

SDR 180658 In BlackBerry Enterprise Server, status messages are not translated or renderedcorrectly.

SDR 365573 In BlackBerry Enterprise Server for IBM Lotus Domino, you cannot map the[Location] field to the PIM Synch Field.




15

The issue was originally caused by an address book mapping issue in IBM LotusNotes. When the BlackBerry Administration Service validates the mapped field, i tdoes not display it if the mapped field does not exist in the mapping on theBlackBerry device.

Workaround: Contact RIM Japan Customer Support for a database script thatupdates the mapping tables.

BlackBerry Enterprise Server

SDR 180933 In the BlackBerry Enterprise Server for IBM Lotus Domino, in rare cases, emailmessages in Japanese are not encoded correctly.

BlackBerry Configuration Database

SDR 298246 If you install the BlackBerry Enterprise Server on a Japanese operating system, youcannot start the BlackBerry database notification system.

BlackBerry Desktop Manager

SDR 180748 In an IBM Lotus Domino environment, a user cannot select folders using theBlackBerry® Desktop Manager to forward messages from the messaging server tothe BlackBerry device.

IT policy

SDR 169887 In BlackBerry Enterprise Server for Microsoft Exchange, IT policy names and itemsdo not support Unicode and some supported Latin characters with accents aredisplayed as black squares on the BlackBerry device.

SDR 178172 The BlackBerry Administration Service seems to accept Latin characters with accentsfor IT policy names and values of IT administrator items, but when you revisit thesetting in the BlackBerry Administration Service, all of the accents disappear. Also,when the values of some IT policy items are applied to the BlackBerry device, theaccents disappear.

Japanese localization

SDR 176809 In BlackBerry Enterprise Server for Microsoft Exchange, when a user creates an

email with “を゛”or “ヲ゛” in the subject line or body of a message in a Japanese

version of Microsoft Outlook, the characters cannot be displayed correctly on theBlackBerry device.

SDR 178289 In BlackBerry Enterprise Server 4.1 SP6, a double-sized hyphen in the address fieldand an asterisk (*) in the comments of a contact lookup are not displayed correctly onthe BlackBerry device. This issue is reproducible on the BlackBerry® Bold™ 9000smartphone.

SDR 182017 In the BlackBerry Enterprise Server for Microsoft Exchange, a Japanese "Inbox"

name on the BlackBerry device does not match that of the email application on theuser’s computer.

SDR 183739 In a BlackBerry Enterprise Server for IBM Lotus Domino environment, if a BlackBerrydevice user creates a meeting request on the BlackBerry device, the meeting requestprefix on the attendee’s device or in the email application is not in the local language.The Invitation prefix is in English characters.

Setup application

SDR 184818 In BlackBerry Enterprise Server, text is cut off at the top of a database configurationSRP screen. This issue occurs in the Japanese language only.

SDR 361403 In the BlackBerry Enterprise Server for Microsoft Exchange, when you remove thesoftware, all the dialog boxes are not translated and display in English.

SDR 249489 The BlackBerry Administration Service displays a comma between the Last Nameand First Name for a user, which impacts searches for user accounts. If you type the




16

full last name and first name of a user into the Display Name field without a comma,the BlackBerry Administration Service does not return a search result.

Workaround: When searching for user accounts, include a comma and a spacebetween the last name and first name.

Wireless calendar synchronization

SDR 190781,

SDR 270737

In BlackBerry Enterprise Server 4.1 or 5.0 SP1, when your organization’senvironment uses Microsoft Exchange 2007, if a user updates a calendarappointment from the BlackBerry device that contains Unicode (Japanese)characters in the subject, location, or message body fields, and sends the update tothe meeting participants, the Japanese characters do not appear correctly (shown asquestion marks) when recipients view the updated calendar appointment in MicrosoftOutlook.




17

Legal notice

©2009 Research In Motion Limited. All Rights Reserved. The BlackBerry and RIM families of related

marks, images, and symbols are the exclusive properties of Research In Motion Limited. RIM, Research

In Motion, BlackBerry, “Always On, Always Connected” and the “envelope in motion” symbol are

registered with the U.S. Patent and Trademark Office and may be pending or registered in othercountries.

IBM, Domino, Lotus, and Lotus Notes are trademarks of International Business Machines Corporation.Microsoft, Excel, Outlook, PowerPoint, TrueType, Windows, and Windows Server are trademarks ofMicrosoft Corporation. Java is a trademark of Sun Microsystems, Inc. DoCoMo is a trademark of NTTDoCoMo, Inc. WinZip is a trademark of WinZip International LLC. All other brands, product names,company names, trademarks and service marks are the properties of their respective owners.

This documentation might contain references to third-party sources of information, hardware or software,products or services including components and content such as content protected by copyright and/orthird-party web sites (collectively the "Third Party Products and Services"). RIM does not control, and isnot responsible for, any Third Party Products and Services including, without limitation the content,accuracy, copyright compliance, compatibility, performance, trustworthiness, legality, decency, links, orany other aspect of Third Party Products and Services. The inclusion of a reference to Third PartyProducts and Services in this documentation does not imply endorsement by RIM of the Third PartyProducts and Services or the third party in any way.

EXCEPT TO THE EXTENT SPECIFICALLY PROHIBITED BY APPLICABLE LAW IN YOURJURISDICTION, ALL CONDITIONS, ENDORSEMENTS, GUARANTEES, REPRESENTATIONS, ORWARRANTIES OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING WITHOUT LIMITATION, ANYCONDITIONS, ENDORSEMENTS, GUARANTEES, REPRESENTATIONS OR WARRANTIES OFDURABILITY, FITNESS FOR A PARTICULAR PURPOSE OR USE, MERCHANTABILITY,MERCHANTABLE QUALITY, NON-INFRINGEMENT, SATISFACTORY QUALITY, OR TITLE, ORARISING FROM A STATUTE OR CUSTOM OR A COURSE OF DEALING OR USAGE OF TRADE, ORRELATED TO THE DOCUMENTATION OR ITS USE, OR PERFORMANCE OR NON-PERFORMANCEOF ANY SOFTWARE, HARDWARE, SERVICE, OR ANY THIRD PARTY PRODUCTS AND SERVICESREFERENCED HEREIN, ARE HEREBY EXCLUDED. YOU MAY ALSO HAVE OTHER RIGHTS THATVARY BY STATE OR PROVINCE. SOME JURISDICTIONS MAY NOT ALLOW THE EXCLUSION OR

LIMITATION OF IMPLIED WARRANTIES AND CONDITIONS. TO THE EXTENT PERMITTED BY LAW,ANY IMPLIED WARRANTIES OR CONDITIONS RELATING TO THE DOCUMENTATION TO THEEXTENT THEY CANNOT BE EXCLUDED AS SET OUT ABOVE, BUT CAN BE LIMITED, AREHEREBY LIMITED TO NINETY (90) DAYS FROM THE DATE YOU FIRST ACQUIRED THEDOCUMENTATION OR THE ITEM THAT IS THE SUBJECT OF THE CLAIM.

TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW IN YOUR JURISDICTION, IN NOEVENT SHALL RIM BE LIABLE FOR ANY TYPE OF DAMAGES RELATED TO THISDOCUMENTATION OR ITS USE, OR PERFORMANCE OR NON-PERFORMANCE OF ANYSOFTWARE, HARDWARE, SERVICE, OR ANY THIRD PARTY PRODUCTS AND SERVICESREFERENCED HEREIN INCLUDING WITHOUT LIMITATION ANY OF THE FOLLOWING DAMAGES:DIRECT, CONSEQUENTIAL, EXEMPLARY, INCIDENTAL, INDIRECT, SPECIAL, PUNITIVE, ORAGGRAVATED DAMAGES, DAMAGES FOR LOSS OF PROFITS OR REVENUES, FAILURE TOREALIZE ANY EXPECTED SAVINGS, BUSINESS INTERRUPTION, LOSS OF BUSINESS

INFORMATION, LOSS OF BUSINESS OPPORTUNITY, OR CORRUPTION OR LOSS OF DATA,FAILURES TO TRANSMIT OR RECEIVE ANY DATA, PROBLEMS ASSOCIATED WITH ANYAPPLICATIONS USED IN CONJUNCTION WITH RIM PRODUCTS OR SERVICES, DOWNTIMECOSTS, LOSS OF THE USE OF RIM PRODUCTS OR SERVICES OR ANY PORTION THEREOF OROF ANY AIRTIME SERVICES, COST OF SUBSTITUTE GOODS, COSTS OF COVER, FACILITIES ORSERVICES, COST OF CAPITAL, OR OTHER SIMILAR PECUNIARY LOSSES, WHETHER OR NOTSUCH DAMAGES WERE FORESEEN OR UNFORESEEN, AND EVEN IF RIM HAS BEEN ADVISEDOF THE POSSIBILITY OF SUCH DAMAGES.

TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW IN YOUR JURISDICTION, RIMSHALL HAVE NO OTHER OBLIGATION, DUTY, OR LIABILITY WHATSOEVER IN CONTRACT, TORT,OR OTHERWISE TO YOU INCLUDING ANY LIABILITY FOR NEGLIGENCE OR STRICT LIABILITY.

THE LIMITATIONS, EXCLUSIONS, AND DISCLAIMERS HEREIN SHALL APPLY: (A) IRRESPECTIVEOF THE NATURE OF THE CAUSE OF ACTION, DEMAND, OR ACTION BY YOU INCLUDING BUTNOT LIMITED TO BREACH OF CONTRACT, NEGLIGENCE, TORT, STRICT LIABILITY OR ANYOTHER LEGAL THEORY AND SHALL SURVIVE A FUNDAMENTAL BREACH OR BREACHES OR




THE FAILURE OF THE ESSENTIAL PURPOSE OF THIS AGREEMENT OR OF ANY REMEDYCONTAINED HEREIN; AND (B) TO RIM AND ITS AFFILIATED COMPANIES, THEIR SUCCESSORS,ASSIGNS, AGENTS, SUPPLIERS (INCLUDING AIRTIME SERVICE PROVIDERS), AUTHORIZED RIMDISTRIBUTORS (ALSO INCLUDING AIRTIME SERVICE PROVIDERS) AND THEIR RESPECTIVEDIRECTORS, EMPLOYEES, AND INDEPENDENT CONTRACTORS.IN ADDITION TO THE LIMITATIONS AND EXCLUSIONS SET OUT ABOVE, IN NO EVENT SHALLANY DIRECTOR, EMPLOYEE, AGENT, DISTRIBUTOR, SUPPLIER, INDEPENDENT CONTRACTOR

OF RIM OR ANY AFFILIATES OF RIM HAVE ANY LIABILITY ARISING FROM OR RELATED TO THEDOCUMENTATION.

Prior to subscribing for, installing, or using any Third Party Products and Services, it is yourresponsibility to ensure that your airtime service provider has agreed to support all of their features.Installation or use of Third Party Products and Services with RIM's products and services may requireone or more patent, trademark, copyright, or other licenses in order to avoid infringement or violation ofthird party rights. You are solely responsible for determining whether to use Third Party Products andServices and if any third party licenses are required to do so. If required you are responsible foracquiring them. You should not install or use Third Party Products and Services until all necessarylicenses have been acquired. Any Third Party Products and Services that are provided with RIM'sproducts and services are provided as a convenience to you and are provided "AS IS" with noexpress or implied conditions, endorsements, guarantees, representations, or warranties of any kind byRIM and RIM assumes no liability whatsoever, in relation thereto. Your use of Third Party Products and

Services shall be governed by and subject to you agreeing to the terms of separate licenses and otheragreements applicable thereto with third parties, except to the extent expressly covered by a license orother agreement with RIM.

The terms of use of any RIM product or service are set out in a separate license or other agreement withRIM applicable thereto. NOTHING IN THIS DOCUMENTATION IS INTENDED TO SUPERSEDE ANYEXPRESS WRITTEN AGREEMENTS OR WARRANTIES PROVIDED BY RIM FOR PORTIONS OFANY RIM PRODUCT OR SERVICE OTHER THAN THIS DOCUMENTATION.

Last modified: December 9, 2009

Documents

BES 5 0 1 Technical Note En