Microsoft KB Archive/814559

= XADM: The Content in the Body Part of a Message Is Different From the Original Message File After You Use CDO to Parse a Multipart Message Stream =

Article ID: 814559

Article Last Modified on 10/26/2006

-

APPLIES TO


 * Microsoft Exchange 2000 Server Standard Edition

-





SYMPTOMS
When you use Collaboration Data Objects (CDO) to parse a multipart MIME message into separate body part streams, the content of a body part stream may not be the same as that of the original .eml message file.



Cumulative Rollup Information
To resolve this problem, obtain the September 2003 Microsoft Exchange 2000 Server Post-Service Pack 3 (SP3) Rollup. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:

824282 September 2003 Exchange 2000 Server Post-Service Pack 3 Rollup

Hotfix Information
A supported hotfix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Only apply it to systems that are experiencing this specific problem. This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next Exchange 2000 Server service pack that contains this hotfix.

To resolve this problem immediately, contact Microsoft Product Support Services to obtain the hotfix. For a complete list of Microsoft Product Support Services telephone numbers and information about support costs, visit the following Microsoft Web site:

http://support.microsoft.com/contactus/?ws=support

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 usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.

Component: CDO

The English version of this hotfix has the file attributes (or later) that are listed in the following table. The dates and times for these files are listed in coordinated universal time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.   Date         Time   Version            Size    File name --  04-Jun-2003  00:46  6.0.6472.0      3,915,776  Cdoex.dll 04-Jun-2003 00:40  6.0.6472.0        827,392  Davex.dll 04-Jun-2003 00:38  6.0.6472.0        577,536  Dsaccess.dll 03-Jun-2003 23:47  6.0.6472.0        184,320  Dscmsg.dll 04-Jun-2003 00:46  6.0.6472.0      3,575,808  Excdo.dll 04-Jun-2003 00:38  6.0.6472.0        258,048  Exmime.dll 04-Jun-2003 00:40  6.0.6472.0      2,138,112  Exoledb.dll 04-Jun-2003 00:36  6.0.6472.0         81,920  Exosal.dll 04-Jun-2003 00:40  6.0.6472.0        307,200  Exprox.dll 03-Jun-2003 23:39  6.0.6472.0         49,152  Mdbevent.dll 04-Jun-2003 00:08  6.0.6472.0      2,285,568  Mdbmsg.dll 03-Jun-2003 23:41  6.0.6472.0         32,768  Mdbrole.dll 04-Jun-2003 00:38  6.0.6472.0         24,576  Mdbtask.dll 04-Jun-2003 00:37  6.0.6472.0      4,648,960  Store.exe Note Because of file dependencies, this update requires Exchange 2000 Server Service Pack 3 (SP3). For additional information, click the following article number to view the article in the Microsoft Knowledge Base:

301378 How to Obtain the Latest Exchange 2000 Server Service Pack



STATUS
Microsoft has confirmed that this is a bug in the Microsoft products that are listed at the beginning of this article.



MORE INFORMATION
For additional information about how to resolve this issue on a Microsoft Windows 2000 Server-based computer where Exchange 2000 Server is not installed, click the following article number to view the article in the Microsoft Knowledge Base:

329631 You Cannot Validate S/MIME Messages with Cdosys.dll

Additional query words: kbExchange2000preSP4septbarFix

Keywords: kbhotfixserver kbqfe kbqfe kbfix kbexchange2000presp4fix kbbug KB814559

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.