XCON: Err Msg: EMS MDB Assert Failure

Last reviewed: February 12, 1998
Article ID: Q176151
The information in this article applies to:
  • Microsoft Exchange Server version 5.0

SYMPTOMS

When you copy a message from an attached PST file to the store, or re-send an old message while there are names in the Reply To field, you may receive the following error message:

   EMS MDB Assert Failure
   Thread 0x123, File 'M:\store\src\store\cp.cxx',Line 1529
   Assert(((fUnicode && cpidSrc == cpidUnicode) || (!fUnicode &&
   cpidSrc != cpidUnicode));

This occurs when the computer running Microsoft Exchange Server is a DEC alpha computer.

CAUSE

This problem may happen when you convert from an unknown SBCS code page to Unicode for existing messages with non-Unicode reply-to-entry IDs. There are two asserts involved. It is possible that the entry ID is in Unicode and the message containing it is not in Unicode.

STATUS

Microsoft has confirmed this to be a problem in Microsoft Exchange Server version 5.0. This problem has been corrected in the latest U.S. Service Pack for Microsoft Exchange Server version 5.0. For information on obtaining the Service Pack, query on the following word in the Microsoft Knowledge Base (without the spaces):

   S E R V P A C K
Keywords          : kbbug5.00 kbfix5.00.sp2 XCON kbusage
Version           : WINDOWS:5.0
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 12, 1998
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.