XFOR: DBCS Messages Not Migrated Correctly from GroupWise

 Last reviewed: February 10, 1998
Article ID: Q179980
The information in this article applies to:
  • Microsoft Exchange Server, version 5.5

SYMPTOMS

When you migrate messages that were created using a double-byte character set (DBCS) from Novell GroupWise, the messages may not be displayed properly when you open them in an e-mail client after the migration.

CAUSE

When you migrate messages from GroupWise, the messages are converted to Rich Text Format (RTF) before they are migrated to the Microsoft Exchange Server computer. Messages that contain DBCS characters may not be converted correctly. Therefore, they may not be displayed properly when you open them in an e-mail client.

STATUS

Microsoft has confirmed this to be a problem in Microsoft Exchange Server version 5.5. A supported fix is now available, but has not been fully regression-tested and should be applied only to systems experiencing this specific problem. Unless you are severely impacted by this specific problem, Microsoft recommends that you wait for the next Service Pack that contains this fix. Contact Microsoft Technical Support for more information.

MORE INFORMATION

GroupWise is manufactured by Novell, a vendor independent of Microsoft; we make no warranty, implied or otherwise, regarding this product's performance or reliability.

Additional query words: japanese japan
Keywords : XFOR kbbug5.50
Version : WINDOWS:5.5
Platform : WINDOWS
Issue type : kbbug
Solution Type : kbfix

THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: February 10, 1998
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.