XADM: Store Crashes When Rich Text Is Enabled over the IMAP4 Protocol

Article translations Article translations
Article ID: 268380 - View products that this article applies to.
This article was previously published under Q268380
This article has been archived. It is offered "as is" and will no longer be updated.
Expand all | Collapse all

SYMPTOMS

The Exchange Server information store may stop responding (crash) and produce a Dr. Watson log and a User.dmp file with the following call stack:
FramePtr  RetAddr   Param1   Param2   Param3   Function Name
054af980  006edf2c  00000000 37020000 054af9e4 STORE!TNEF_AddProps+0x348
054afa10  0047ce0c  00000000 37020000 054af9e4 STORE!CmnBptMessage::hrTNEFAttach+0xc0
054afa50  0047cba4  00000000 37020000 054af9e4 STORE!CRFCMIMEemtr::hrEndOfBody+0x200
054afab0  0047909c  00000000 00000000 054af9e4 STORE!CmcvtrBdy::hrEmit+0x190
054afb00  00478f80  00000000 00000000 054af9e4 STORE!CINETemtr::hrEmit+0x100
054afb40  004a3430  00000000 00000000 054af9e4 STORE!CConvertStream::Read+0x11c
054afb80  004a2674  00000000 00000000 054af9e4 STORE!MCE::EcRenderBodyPart+0x25c
054afbf0  0049e004  00000000 00000000 054af9e4 STORE!MCE::EcDetermine822Size+0x120
054afc90  0049e8b0  00000000 00000000 054af9e4 STORE!IMAPCON::EcProcessFetchInfo+0x290
054afcd0  004a494c  00000000 00000000 054af9e4 STORE!IMAPCON::EcQueueFetchSet+0x128
054afd20  004a4f80  00000000 00000000 054af9e4 STORE!IMAPCON::EcProcessFetchSet+0x198
054afd90  004a1f50  00000000 00000000 054af9e4 STORE!IMAPCON::CbFetch+0x5bc
054afdf0  004a1340  00000000 00000000 054af9e4 STORE!IMAPCON::CbUid+0xe0
054afe30  6fcc8d24  00000000 00000000 054af9e4 STORE!IMAPCON::CbCommand+0xd08
					

CAUSE

An IMAP user has sent a command that the information store does not process correctly. The following command may cause this issue:
007H FETCH 1 (INTERNALDATE RFC822.SIZE FLAGS ENVELOPE BODY UID)
NOTE: The 007H and the 1 following the FETCH command may be different depending on conversation key and the message being accessed.

You can configure the IMAP protocol in the Exchange Server Administrator program to allow Rich Text Format (RTF). This setting enables the IMAP protocol to encode any OLE-embedded objects into a TNEF stream. When the preceding command is given to the IMAP service to retrieve a message with an embedded OLE object, such as a Clip Art picture, the preceding command may cause the store to crash. When the preceding command cannot correctly encode the OLE object into a TNEF stream. The preceding command works correctly when the setting to allow RTF is not set in the Administrator program.

RESOLUTION

To resolve this problem, obtain the latest service pack for Exchange Server 5.5. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
191914 XGEN: How to Obtain the Latest Exchange Server 5.5 Service Pack
The following files are available for download from the Microsoft Download Center:
x86:
Collapse this imageExpand this image
Download
Download Q248838engi.exe now
Alpha:
Collapse this imageExpand this image
Download
Download Q248838enga.exe now
For additional information about how to download Microsoft Support files, click the following article number to view the article in the Microsoft Knowledge Base:
119591 How to Obtain Microsoft Support Files from Online Services
Microsoft scanned this file for viruses. Microsoft used the most current virus-detection software that was available on the date that the file was posted. The file is stored on security-enhanced servers that help to prevent any unauthorized changes to the file.

WORKAROUND

You can turn off the option to allow RTF in the Administrator program. To do so:
  1. Start the Administrator program, and connect to the server that is experiencing this issue.
  2. Locate the Site\Configuration\Protocols object.
  3. Double-click the IMAP4 object in the right pane.
  4. Click the Message Format tab.
  5. Click to clear the Use Microsoft Exchange rich-text format check box.

STATUS

Microsoft has confirmed that this is a problem in Microsoft Exchange Server version 5.5. This problem was first corrected in Exchange Server 5.5 Service Pack 4.

Properties

Article ID: 268380 - Last Review: October 20, 2013 - Revision: 4.2
APPLIES TO
  • Microsoft Exchange Server 5.5 Standard Edition
  • Microsoft Exchange Server 5.5 Service Pack 1
  • Microsoft Exchange Server 5.5 Service Pack 2
  • Microsoft Exchange Server 5.5 Service Pack 3
Keywords: 
kbnosurvey kbarchive kbhotfixserver kbqfe kbbug kbexchange550presp4fix kbfix kbqfe KB268380

Give Feedback

 

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com