Microsoft KB Archive/871187

= Issues that may occur when you use Outlook Mobile Access with mobile devices and with the iMode service from NTT DoCoMo =

Article ID: 871187

Article Last Modified on 10/25/2007

-

APPLIES TO


 * Microsoft Exchange Server 2003 Enterprise Edition
 * Microsoft Exchange Server 2003 Standard Edition

-



IN THIS TASK

 * INTRODUCTION
 * You cannot use emoji characters in some sections of Outlook Mobile Access
 * You are prompted for authentication two times when you use Outlook Mobile Access with the SO505i mobile device from NTT DoCoMo



INTRODUCTION
The following issues may occur when you try to use Microsoft Outlook Mobile Access with mobile devices and the iMode service from NTT DoCoMo, Inc. Each section describes the symptom and the cause of an issue. Additionally, each section offers a workaround if one is available.

back to the top



Symptom
Emoji characters are the Japanese equivalent of emoticons. When you try to use an emoji character in an Outlook Mobile Access message on a mobile device from NTT DoCoMo, the emoji character turns into a question mark.

Cause
This issue is caused by the way that characters are encoded on the NTT DoCoMo mobile device. Emojis work correctly in the tasks, in the calendar items, and in the contacts sections of Outlook Mobile Access. However, emojis will not work in mail sections. By default, the UseRegionalCharset registry subkey is turned on so that Japanese users can use Japanese to send messages. Additionally, mail is encoded in ISO-2022-jp by default. Emojis are non-standard ISO-2022-jp and are not encoded correctly. If the UseRegionalCharset registry subkey is turned off, mail is encoded in UTF-8, and the emojis work. Emojis work in the tasks, in the calendar items, and in the contacts sections of Outlook Mobile Access regardless of the registry key setting because the items in these sections are all encoded in UTF-8.

Workaround
There is no workaround for this issue.

back to the top

Symptom
When you try to access Outlook Mobile Access in a Secure Sockets Layer (SSL) session, you are prompted for your credentials again after you enter your credentials for authentication.

Cause
This problem occurs if you do not include a forward slash at the end of the Outlook Mobile Access SSL URL. For example, if you type https:// /oma instead of https:// /oma/, this issue occurs.

Workaround
To work around this problem, include a forward slash at the end of the URL when you type the SSL URL for Outlook Mobile Access. For example, type https:// /oma/.

back to the top

The third-party products that this article discusses are manufactured by companies that are independent of Microsoft. Microsoft makes no warranty, implied or otherwise, regarding the performance or reliability of these products.

Keywords: kb3rdparty kbtshoot kbmobility kbprb kbinfo KB871187

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.