Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

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


View products that this article applies to.

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


More information

Emoji characters cannot be used in some sections of Outlook Mobile Access

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.

You are prompted for authentication two times when you use Outlook Mobile Access with the SO505i mobile device from NTT DoCoMo

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://Exchange_Server/oma instead of https://Exchange_Server/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://Exchange_Server/oma/.



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.

↑ Back to the top


Keywords: KB871187, kbinfo, kbprb, kbmobility, kbtshoot, kb3rdparty

↑ Back to the top

Article Info
Article ID : 871187
Revision : 4
Created on : 10/25/2007
Published on : 10/25/2007
Exists online : False
Views : 265