Describes an issue that occurs when you reply to or forward a message in an Exchange Server 2007 SP1, Exchange Server 2010, or Exchange Server 2010 SP1 environment. Japanese DBCS characters in the original message are corrupted. A resolution is provided.

This issue occurs because the value of the PR_INTERNET_CPID MAPI property of the message is stamped as 50222 by Exchange RPC Client Access service or Outlook Web App. Because of a restriction in Outlook, the code page 50222 characters are corrupted.

Fixes an issue in which Japanese DBCS characters are corrupted. This issue occurs when you send a meeting request or post a reply to a posted item in a public folder by using the OWA in an Exchange Server 2010 environment.

When inputting some characters using the IME Pad in the Microsoft Japanese IME, the wrong characters might be outputted. For example, if you choose “。”, (0xA1) from [Half width Alpha] under [Shift JIS], the character “>” will be outputted.

Fixes an issue occurs when you set the COLLATE clause to Japanese_XJIS_100_CI_AS in SQL Server 2008 R2, SQL Server 2012, or SQL Server 2014.

When you import Japanese Double-Byte Character Set (DBCS) characters in Microsoft Dynamics NAV 2013, they are displayed as garbled characters. Cause. This problem occurs because of a regression in XML Port handling of DBCS Data. Resolution. Hotfix information. A supported hotfix is available from Microsoft.

Japanese customers have reported issues with the readability of some parts of Outlook Desktop. We’ve heard your feedback and implemented several fixes to address those concerns. The Segoe UI font has been replaced by the more language-appropriate Meiryo font in the following areas:

Describes an issue in which an access violation occurs when a database table name contains Japanese characters. Provides a resolution.

When you receive a Skype for Business online meeting invitation that's created by Japanese version of Skype for Business 2016, you may find the email is garbled, and many Japanese characters can't be recognized. Resolution. To fix this issue, install the July 10, 2018, security update for Skype for Business 2016 (KB4022221).

In this scenario, Japanese characters in the subject line of the missed call notification email message are garbled. Cause. This issue occurs because the user notification XML file that is sent by Lync Server is encoded by using US-ASCII instead of UTF8. Resolution