XWEB: Some Japanese-Language Characters Become Question Marks After You Apply the Q283214 Fix (313143)
The information in this article applies to:
- Microsoft Exchange 2000 Server
This article was previously published under Q313143 SYMPTOMS
Some Shift-JIS characters in a message body may become question marks (?) if:
- The environment is a Japanese-language Exchange 2000 Server Service Pack 2 (SP2) environment.
- You applied the fix that is described in the following Microsoft Knowledge Base article:
283214 XCCC: Outlook Web Access May Send a Japanese-Language Message in SJIS
- You set the UseAltRegionalCharset registry value that is also described in Knowledge Base article Q283214.
- You used Microsoft Outlook Web Access (OWA) to send the message.
The following table contains the Shift-JIS characters that are affected. |
| Fullwidth tilde | 0x8160 | U+FF5E | | Parallel to | 0x8161 | U+2225 | | Fullwidth hyphen-minus sign | 0x817c | U+FF0D | | Fullwidth cent sign | 0x8191 | U+FFE0 | | Fullwidth number sign | 0x8192 | U+FFE1 | | Fullwidth not sign | 0x8192 | U+FFE2 | | Fullwidth broken bar | 0xFA55 | U+FFE4 |
CAUSE
This problem occurs because of mismatches in character mapping between JIS X 0201-1995 and code page 932 (known as Shift-JIS). Because of these mismatches, these characters become question marks during the character conversion.
RESOLUTIONTo resolve this problem, obtain the latest service pack for Microsoft Exchange 2000 Server. For additional information, click the following article number to view the article in the
Microsoft Knowledge Base:
301378 XGEN: How to Obtain the Latest Exchange 2000 Server Service Pack
The version of this fix should have the following file attributes or later:
Component: Information store
|
| Store.exe | 6.0.5770.1 | | Davex.dll | 6.0.5770.1 | | Excdo.dll | 6.0.5770.1 | | Exoledb.dll | 6.0.5770.1 | | Exprox.dll | 6.0.5770.1 | | Jcb.dll | 6.0.5770.1 | | Mdbsz.dll | 6.0.5770.1 |
NOTE: Because of file dependencies, this update requires Microsoft Exchange 2000 Server Service Pack 2.
STATUSMicrosoft has confirmed that this is a problem in Microsoft Exchange 2000 Server. This problem was first corrected in Microsoft Exchange 2000 Server Service Pack 3.
| Modification Type: | Minor | Last Reviewed: | 6/6/2003 |
|---|
| Keywords: | kbbug kbExchange2000preSP3fix kbExchange2000sp3fix kbfix KB313143 |
|---|
|