This article was previously published under Q311437
This article has been archived. It is offered "as is" and will no longer be updated.
In a Japanese-language Exchange 2000 Server environment, after you apply the fix and set the UseAltRegionalCharset registry value that are both described in the following Microsoft Knowledge Base article
283214 XCCC: Outlook Web Access May Send a Japanese-Language Message in SJIS
if you use Microsoft Outlook Web Access (OWA) to send a message, the following Shift-JIS characters in the message body may become question marks (?).
Fullwidth cent sign
Fullwidth pound sign
Fullwidth not sign
Fullwidth broken bar
This problem can occur because of mismatches in character mapping between JIS X 0201-1995 and code page 932 (known as Shift-JIS); as a result, these characters become question marks during the character conversion.
A supported fix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Apply it only to computers that are experiencing this specific problem. This fix may receive additional testing. Therefore, if you are not severely affected by this problem, Microsoft recommends that you wait for the next Microsoft Exchange 2000 Server service pack that contains this hotfix.
To resolve this problem immediately, contact Microsoft Product Support Services to obtain the fix. For a complete list of Microsoft Product Support Services phone numbers and information about support costs, visit the following Microsoft Web site:
NOTE: In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The typical support costs will apply to additional support questions and issues that do not qualify for the specific update in question.
The version of this fix should have the following file attributes or later:
Component: Information store
NOTE: Because of file dependencies, this update requires Microsoft Exchange 2000 Server Service Pack 1.
Microsoft has confirmed that this is a problem in Microsoft Exchange 2000 Server.