XCLN: MAPI Spooler Sends NDRs During Folder Synchronization

Retired KB Content Disclaimer

View products that this article applies to.

This article was previously published under Q192533

Expand all | Collapse all

SYMPTOMS

If an application posts a message to the user's outbox during the time the application is synchronizing the user's outbox, the MAPI spooler sends a non-delivery report (NDR) on this newly submitted message with the following error message:

   Your message did not reach some or all of the intended recipients.

      Subject: Extended MAPI message 11001.
      Sent: 11/24/97 4:44:59 PM

   The following recipient(s) could not be reached:

      <RECIPIENT NAME>
      No transport provider was available for delivery to this recipient.

Back to the top

CAUSE

This problem is caused by a logic error in the way the emsmdb32 provider handles messages posted during synchronization.

Back to the top

RESOLUTION

To resolve this problem, obtain the latest service pack for Exchange Server version 5.5. For more information, please see the following article in the Microsoft Knowledge Base:

191014 (http://support.microsoft.com/kb/191014/EN-US/ ) XGEN: How to Obtain the Latest Exchange Server 5.5 Service Pack

The English version of this fix should have the following file attributes or later:

Component: Provider

   File Name      Version
   ----------------------
   Emsui32.dll    2326.0
   Mspst32.dll    2326.0
   Emsmdb32.dll   2326.0

Back to the top

STATUS

Microsoft has confirmed this to be a problem in Microsoft Exchange Server versions 4.0, 5.0, and 5.5.

Back to the top

APPLIES TO

Microsoft Exchange Server 4.0 Standard Edition
Microsoft Exchange Server 5.0 Standard Edition
Microsoft Exchange Server 5.5 Standard Edition
Microsoft Outlook 97 Service Pack 1
Microsoft Outlook 97 Standard Edition
Microsoft Outlook 98 Standard Edition

Back to the top

kbqfe kbhotfixserver kbbug kbfix KB192533

Back to the top

Retired KB Content Disclaimer

This article was written about products for which Microsoft no longer offers support. Therefore, this article is offered "as is" and will no longer be updated.

Back to the top