XADM: Access Violation in Store.exe Because of Malformed TNEF Stream

This article was previously published under Q304223
This article has been archived. It is offered "as is" and will no longer be updated.
When the information store attempts to process an inbound Simple Mail Transfer Protocol (SMTP) message, an access violation may occur. If you review the User.dmp file or if the proper Exchange 2000 symbols are installed at the time of the access violation, the Dr.Watson log file may contain a call stack that is similar to the following:
The following may appear in the Dr. Watson Log:
FAULT ->007a6fe7 8b5108           mov     edx,[ecx+0x8]          ds:0081d5d2=00000000        007a6fea 8d442410         lea     eax,[esp+0x10]         ss:2738cbf7=????????        007a6fee 50               push    eax        007a6fef 8b442424         mov     eax,[esp+0x24]         ss:2738cbf7=????????        007a6ff3 81e200800000     and     edx,0x8000        007a6ff9 83ca01           or      edx,0x1        007a6ffc 52               push    edx        007a6ffd 50               push    eax        007a6ffe e8d68bd0ff       call    004afbd9        007a7003 8bf0             mov     esi,eax        007a7005 3bf5             cmp     esi,ebp        007a7007 0f8cb8000000     jl      007a70c5					
When the information store attempts to process an inbound SMTP message that contains a Transport-Neutral Encapsulation Format (TNEF) data attachment, the information store attempts to fully convert the message to Message Database Encapsulated Format (MDBEF) format in the information store, and then promote the message to the .edb file instead of leaving the message in native Multipurpose Internet Mail Extensions (MIME) format in the .stm file. This problem can occur if a PR_RTF_COMPRESSED property is present in the stream, but does not contain any Rich Text Format (RTF) data.
A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem.

If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, submit a request to Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site: Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language. The English version of this fix should have the following file attributes or later:

Component: Information store

File nameVersion

NOTE: Because of file dependencies, this update requires Microsoft Exchange Server 2000 Service Pack 1.
Microsoft has confirmed that this is a problem in Microsoft Exchange 2000 Server.

Article ID: 304223 - Last Review: 10/24/2013 07:09:05 - Revision: 1.6

  • Microsoft Exchange 2000 Server Standard Edition
  • kbnosurvey kbarchive kbautohotfix kbhotfixserver kbbug kbexchange2000presp2fix kbfix kbqfe KB304223