DOCUMENT:Q302935 08-MAY-2002 [exchange] TITLE :XADM: Truncated Text Returned If CDO Runs as a Service PRODUCT :Microsoft Exchange PROD/VER::5.5,5.5 SP1,5.5 SP2,5.5 SP3,5.5 SP4 OPER/SYS: KEYWORDS:kbExchange550preSP5fix ====================================================================== ------------------------------------------------------------------------------- The information in this article applies to: - Microsoft Exchange Server, versions 5.5, 5.5 SP1, 5.5 SP2, 5.5 SP3, 5.5 SP4 ------------------------------------------------------------------------------- SYMPTOMS ======== When you run the Collaboration Data Objects (CDO) application as a Microsoft Windows NT service, if a message body contains double-byte character set (DBCS) characters, the Exchange Server information store may return a truncated message body. CAUSE ===== When the CDO application runs as a Windows NT service, CDO uses Unicode text to get the message body. Because the message body is stored as American National Standards Institute (ANSI) text, the Exchange Server information store converts the ANSI text to Unicode text. This problem can occur during the conversation if a DBCS character spans the 16 kilobyte (KB) boundary. RESOLUTION ========== A supported fix is now available from Microsoft, but it is only intended to correct the problem described in this article and should be applied only to systems experiencing this specific problem. This fix may receive additional testing at a later time, to further ensure product quality. Therefore, if you are not severely affected by this problem, Microsoft recommends that you wait for the next Microsoft Exchange Server 5.5 service pack that contains this fix. 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, please go to the following address on the World Wide Web: http://support.microsoft.com/default.aspx?scid=fh;EN-US;CNTACTMS NOTE: In special cases, charges that are normally incurred for support calls may be canceled, if a Microsoft Support Professional determines that a specific update will resolve your problem. Normal support costs will apply to additional support questions and issues that do not qualify for the specific update in question. The English version of this fix should have the following file attributes or later: Component: Information store +-------------------------+ | File name | Version | +-------------------------+ | Store.exe | 5.5.2655.37 | +-------------------------+ NOTE: Because of file dependencies, this fix requires Microsoft Exchange Server version 5.5 Service Pack 4. STATUS ====== Microsoft has confirmed this to be a problem in Microsoft Exchange Server version 5.5. Additional query words: MAPI 16383 16384 Japanese automation ====================================================================== Keywords : kbExchange550preSP5fix Technology : kbExchangeSearch kbExchange550 kbZNotKeyword2 kbExchange550SP1 kbExchange550SP2 kbExchange550SP3 kbExchange550SP4 Version : :5.5,5.5 SP1,5.5 SP2,5.5 SP3,5.5 SP4 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. Copyright Microsoft Corporation 2002.