Article ID: 321657 - View products that this article applies to.
This article was previously published under Q321657
This article has been archived. It is offered "as is" and will no longer be updated.
When Exchange 2000 converts a message from Multipurpose Internet Mail Extensions (MIME) to Rich Text Format (RTF), an access violation may occur.
If Exchange 2000 processes a message that contains a MIME header that indicates that an attachment exists, and the attachment has been removed (possibly by a virus scanner), an access violation may occur. If the correct symbols are installed at the time of the access violation, a Drwtsn32.log file or the User.dmp file may contain a call stack that is similar to:
ChildEBP RetAddr 0f36eff4 00752f70 store!ATTMCVT::HrGetNativeCpid+0x26 0f36f444 00440a9f store!ScProcessHtmlbase+0x173 0f36f470 004a2eae store!RTFHTML::ScUnwindTokens+0xac 0f36f4a4 00752649 store!RTFHTML::ScPopRTFState+0x97 0f36f4cc 00440514 store!ScProcessHtmltag+0x356 0f36f4ec 00440424 store!RTFHTML::ScNInterpret+0x25 0f36f4f8 0042f671 store!RTFHTML::ScInterpret+0xb 0f36f54c 0042fee5 store!OUTPOP::Read+0x286 0f36f5b0 0042fdae store!OUTPOP::CopyTo+0x101 0f36f61c 0042fcbf store!OUTPOP::HrConvert+0xd2 0f36f654 0042de37 store!OUTPOP::Stat+0x53 0f36f6c8 004285b9 store!STREAM::EcGetSize+0x191 0f36f6e8 004d20e3 store!EcOpenStream2+0x174 0f36f720 004b59a9 store!EcOpenStreamOp2+0xa0 0f36f754 004b5909 store!EcOpenStreamOp+0x5a 0f36f7b0 004d1ccb store!EcOpenStream+0x141 0f36f8d4 004d1083 store!EcRpc+0x1ca4 0f36f8ec 77d43b58 store!EcDoRpc+0x60 0f36f910 77da2577 RPCRT4!Invoke+0x30
To resolve this problem, obtain the latest service pack for Microsoft Exchange 2000 Server. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
301378The English version of this fix has the following file attributes or later:
(http://support.microsoft.com/kb/301378/EN-US/ )XGEN: How to Obtain the Latest Exchange 2000 Server Service Pack
Component: Information store
Collapse this tableExpand this table
NOTE: Because of file dependencies, this update requires Microsoft Exchange 2000 Server Service Pack 2.
Microsoft has confirmed that this is a problem in Microsoft Exchange 2000 Server. This problem was first corrected in Microsoft Exchange 2000 Server Service Pack 3.