XFOR: Japanese Characters in Subject Line Are Question Marks After Migration by Ccmarch.exe Program (279175)



The information in this article applies to:

  • Microsoft Exchange Server 5.5 SP2
  • Microsoft Exchange Server 5.5 SP3
  • Microsoft Exchange Server 5.5 SP4

This article was previously published under Q279175

SYMPTOMS

If you migrate from a Lotus cc:Mail archive to a Microsoft Outlook personal folder (.pst) file by using the Japanese-language version of the Microsoft Importer for Lotus cc:Mail Archives (Ccmarch.exe), the Japanese characters in the subject line may be replaced with question marks (???).

CAUSE

This problem occurs because the code page that is used in the translation function is not correct, which renders Japanese characters unreadable. The unreadable Japanese characters are displayed as question marks (???) in the subject line of the message.

RESOLUTION

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 Exchange Server 5.5 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.

This fix should have the following file attributes or later:

Component: Microsoft Exchange Connector for Lotus cc:Mail

File nameVersion
Ccmarch.exe5.5.2654.41

STATUS

Microsoft has confirmed that this is a problem in Exchange Server version 5.5 Service Pack 2, Service Pack 3, and Service Pack 4.

Modification Type:MinorLast Reviewed:8/23/2006
Keywords:kbHotfixServer kbQFE kbbug kbfix kbQFE KB279175