Microsoft KB Archive Search

Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

  1. Home
  2. XADM: Mail Is Stuck in Outbox Because of Infinite Loop in Information Store

XADM: Mail Is Stuck in Outbox Because of Infinite Loop in Information Store

View products that this article applies to.

This article was previously published under Q311722

↑ Back to the top

Symptoms

If you send a message that contains an attachment, the message may stay in the Outlook Outbox and not be sent. The message stays displayed in italic format.

↑ Back to the top

Cause

This problem can occur if the information store send threads are caught in an infinite loop when trying to read information out of a message. If a user sends a message that contains an attachment and the virus scanning application programming interface (virus scanning API) is enabled, the attachment must be sent through the scanner to ensure that the attachment is not infected. If the attachment is infected or flagged for removal, the attachment can be replaced by another file (usually a text file) that alerts the user or administrator that the attachment has been replaced. During this replacement process, the information store needs to read in properties again, but cannot. The thread enters an infinite loop, which causes the message to sit in the Outbox and not be sent. This problem can occur for multiple users and for multiple messages from the same user.

↑ Back to the top

Resolution

A supported fix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Apply it only to computers that are experiencing this specific problem. This fix may receive additional testing. 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 hotfix.

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, visit the following Microsoft Web site:
http://support.microsoft.com/default.aspx?scid=fh;EN-US;CNTACTMS
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 typical 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 nameVersion
Store.exe5.5.2655.62

NOTE: Because of file dependencies, this fix requires Microsoft Exchange Server version 5.5 Service Pack 4.

↑ Back to the top

Status

Microsoft has confirmed that this is a problem in Microsoft Exchange Server version 5.5.

↑ Back to the top

More information

One or more threads may have a call stack that is similar to the following; these threads might also consume high CPU: 
ChildEBP RetAddr  Args to Child              
036df6dc 77f1cca0 00000f70 00000000 00000000 ntdll!NtWaitForSingleObject+0xb
036df704 6feafc13 00000f70 ffffffff 00000000 KERNEL32!WaitForSingleObjectEx+0x73
036df740 6fe97cf0 036df8d0 003b8000 15d83bd8 ESE!CRIT___Enter+0x27f
036df760 6fe99e7a 00000001 036df878 036df808 ESE!ErrDIRBeginTransaction+0xaf
036df79c 6fe99d48 00000107 3c60e010 00003800 ESE!ErrIsamRetrieveColumn+0x9e
036df808 00408da0 06150900 15d83bd8 00000107 ESE!JetRetrieveColumn+0x150
036df858 0040177a 036df878 3c60e010 00003800 store!JTAB_BASE__EcRetrieveColumnByPtagid+0x115
036df880 00450969 37010102 3c60e010 00003800 store!JTAB_BASE__EcRetrieveColumn+0x36
036df8dc 00510760 3c60e010 00003800 036df910 store!STREAM__EcRead+0x339
036df914 0051032e 3c3e32c8 00000000 1e561ab0 store!EcStreamOutPprvIntoOMB+0x1ad
036df94c 004c9caa 1e561ab0 00000000 00000000 store!EcMDBEFFromAttach+0x20c
036dfb78 004c94b7 00000001 00000001 00000000 store!EcMDBEFFromMessage+0x9dc
036dfba0 005fc0a3 00000000 ffffffff 00000001 store!EcCreateMDBEF+0x70
036dfc9c 004b2017 00cbbbec 1ae098e8 036dfcf0 store!EcCreateOMSubmit+0x9a7
036dfd6c 004d4429 1ae098e8 01052ee0 036dfd9c store!EcSendMessage+0xb5
036dffa0 004df61d 77f9d870 ffffffff 036dffec store!FStartSend+0x842
036dffb8 77f04ede 00000000 77f9d870 ffffffff store!EcProcessTask+0x11c
ffffffff 00000000 00000000 00000000 00000000 KERNEL32!BaseThreadStart+0x51

↑ Back to the top

Keywords: kbhotfixserver, kbqfe, kbbug, kbexchange550presp5fix, kbfix, kbqfe, KB311722

↑ Back to the top

Article Info
Article ID : 311722
Revision : 7
Created on : 10/26/2006
Published on : 10/26/2006
Exists online : False
Views : 398