Microsoft KB Archive/832128

= Issues that may occur when you use Outlook Mobile Access with the au mobile devices from KDDI Corporation =

Article ID: 832128

Article Last Modified on 10/25/2007

-

APPLIES TO


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

-



INTRODUCTION
This article describes issues that may occur when you use Microsoft Outlook Mobile Access with the au mobile devices from KDDI Corporation.



MORE INFORMATION
The following issues may occur when you try to use Outlook Mobile Access with the browser on all au mobile devices from KDDI Corporation.
 * Symptom

You use your au mobile device to make a call through a Wireless Telephony Applications Interface (WTAI) link, and then you end the call. When you try to continue your data session with Outlook Mobile Access, you are prompted for authentication.

Cause

This issue occurs because au mobile devices do not suspend a data session when a call session is started. Instead, the data session is closed when a call session is made. When the call session is closed, a new data session must be started. Therefore, you are prompted for authentication. After authentication is completed, your data session with Outlook Mobile Access resumes.

Workaround

There is currently no workaround for this issue.
 * Symptom

You cannot use Outlook Mobile Access when you try to use a Secure Sockets Layer (SSL) session to connect to a server that is running Microsoft Exchange Server.

Cause

This issue occurs if the Exchange Server computer is running Microsoft Windows 2000 Service Pack 3 (SP3) or earlier.

Workaround

To work around this issue, install Windows 2000 Service Pack 4 (SP4) or later on the server that is running Exchange.
 * Symptom

You cannot type emojis in Outlook Mobile Access on an au mobile device. (Emojis are Japanese symbols that are similar to the emoticons that are used in English e-mail.) The emoji input option is not available (appears dimmed) in the Input Method Editor of the device browser.

Cause

This issue occurs because the au mobile devices are designed to use only roman characters, numeric characters, and the following types of Japanese characters: hiragana, katakana, and kanji.

Workaround

There is currently no workaround for this issue.

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: kbmobility kbprb kbinfo KB832128

-

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

© Microsoft Corporation. All rights reserved.