Microsoft KB Archive/823491

= You Receive a Non-Delivery Report After an Extended Period of Time and Event ID 327 Is Logged in the Application Log =

Article ID: 823491

Article Last Modified on 10/26/2006

-

APPLIES TO


 * Microsoft Exchange 2000 Server Standard Edition

-





SYMPTOMS
When you try to send an e-mail message, you receive a non-delivery report (NDR) after an extended period of time (for example, two days later). The NDR contains information that is similar to the following information:

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

Subject:

Sent:

The following recipient(s) could not be reached:

on

The e-mail system was unable to deliver the message, but did not report a specific reason. Check the address and try again. If it still fails, contact your system administrator.

When you view the application log in Windows Event Viewer on your Exchange 2000 computer, you see the following event logged every five minutes: Event Type: Warning

Event Source: MSExchangeTransport

Event Category: Exchange Store Driver

Event ID: 327

Computer:

Description:

The following call : EcGetMime to the store failed. Error code : -2147024809. MDB : 87354ede-8a7b-4a27-8778-2e7b84422acd. FID : 1-123. MID : 1-1918B1D. File :.



CAUSE
This problem may occur if a mail message is stuck in the local delivery queue. A mail message may become stuck in the local delivery queue if the message content is corrupted during the content conversion from MAPI to MIME. MIME conversion fails if there is some data in the message that the IMAIL component cannot map to MIME.



Hotfix Information
A supported hotfix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Only apply it to systems that are experiencing this specific problem. This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next Microsoft Exchange 2000 Server service pack that contains this hotfix.

To resolve this problem immediately, contact Microsoft Product Support Services to obtain the hotfix. For a complete list of Microsoft Product Support Services telephone numbers and information about support costs, visit the following Microsoft Web site:

http://support.microsoft.com/contactus/?ws=support

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 usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.

Prerequisites
Because of file dependencies, this update requires Microsoft Exchange 2000 Server Service Pack 3 (SP3). For additional information, click the article number below to view the article in the Microsoft Knowledge Base:

301378 How to Obtain the Latest Exchange 2000 Server Service Pack

File Information
The English version of this fix has the file attributes (or later) that are listed in the following table. The dates and times for these files are listed in coordinated universal time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.

Date        Time   Version     Size       File name - 31-Jul-2003 19:02  6.0.6493.0  3,915,776  Cdoex.dll 31-Jul-2003 18:57  6.0.6493.0    851,968  Davex.dll 31-Jul-2003 18:57  6.0.6493.0     53,248  Davexpc.dll 31-Jul-2003 18:54  6.0.6493.0    131,072  Drviis.dll 31-Jul-2003 18:54  6.0.6493.0    577,536  Dsaccess.dll 31-Jul-2003 18:00  6.0.6493.0    184,320  Dscmsg.dll 31-Jul-2003 18:01  6.0.6493.0    958,464  Emsmdb32.dll 31-Jul-2003 19:02  6.0.6493.0  3,575,808  Excdo.dll 31-Jul-2003 18:55  6.0.6493.0    258,048  Exmime.dll 31-Jul-2003 18:57  6.0.6493.0    143,360  Exodbesh.dll 31-Jul-2003 18:57  6.0.6493.0     57,344  Exodbpc.dll 31-Jul-2003 18:57  6.0.6493.0    200,704  Exodbprx.dll 31-Jul-2003 18:57  6.0.6493.0  2,174,976  Exoledb.dll 31-Jul-2003 18:53  6.0.6493.0     81,920  Exosal.dll 31-Jul-2003 18:57  6.0.6493.0    307,200  Exprox.dll 31-Jul-2003 18:00  6.0.6493.0    143,360  Exschema.exe 31-Jul-2003 18:57  6.0.6493.0    315,392  Exsmtp.dll 31-Jul-2003 18:00  6.0.6493.0    675,840  Exwform.dll 31-Jul-2003 17:54  6.0.6493.0     49,152  Mdbevent.dll 31-Jul-2003 17:58  6.0.6493.0  2,285,568  Mdbmsg.dll 31-Jul-2003 17:55  6.0.6493.0     32,768  Mdbrole.dll 31-Jul-2003 18:55  6.0.6493.0     24,576  Mdbtask.dll 31-Jul-2003 18:53  6.0.6493.0     94,208  Peexch50.dll 31-Jul-2003 18:53  6.0.6493.0    397,312  Phatcat.dll 31-Jul-2003 18:55  6.0.6493.0    528,384  Reapi.dll 31-Jul-2003 18:57  6.0.6493.0    311,296  Resvc.dll 31-Jul-2003 18:54  6.0.6493.0  4,657,152  Store.exe



STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.

Keywords: kbhotfixserver kbqfe kbqfe kbfix kbexchange2000presp4fix kbbug KB823491

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.