On an Exchange Server 2003 server, messages
stay in the local delivery queue and keep retrying until you
manually delete them. Additionally, the following event is logged in
the Application log:
Event Type: Warning
Event Source: MSExchangeTransport
Event Category: Exchange Store Driver
Event ID: 327
Description: The following call : EcLocallyDeliverMsg to the store failed.
Error code : -2147024882 (Message-ID xxxx). MDB : xxxx. FID : xxxx
Error code -2147024882 maps to "MAPI_E_NOT_ENOUGH_MEMORY"
This problem occurs because the References field of these
messages is larger than 8 KB. Exchange Server does not correctly handle the
messages in this situation.
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 the problem described in this article. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.
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, contact 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.
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 Server 2003 service pack that contains this
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: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.
This hotfix requires Microsoft Exchange Server 2003 Service
Pack 2 to be installed on the server because of file dependencies.
For more information, click the following article number to view the article in the Microsoft Knowledge Base:
How to obtain the latest service packs for
Exchange Server 2003
You do not have to restart the computer after you apply this hotfix. However, the following services are restarted automatically when you
apply this hotfix:
- The Microsoft Exchange Information Store service
- The Microsoft Search service
- The Internet Information Services (IIS) Admin Service and
all dependent services
Hotfix replacement information
This hotfix does not replace a previously released hotfix.
The English version of this hotfix has the file attributes (or later file attributes) 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
item in Control Panel.
Collapse this tableExpand this table
|File name||File version||File
The References field is defined in RFC 2822 that is used
to identify a "thread" of conversation. For more information about the
References field, visit the following Web site:
has confirmed that this is a problem in the Microsoft products that are listed
in the "Applies to" section.
Article ID: 951558 - Last Review: February 5, 2009 - Revision: 1.0
- Microsoft Exchange Server 2003 Standard Edition
- Microsoft Exchange Server 2003 Enterprise Edition
|kbsurveynew kbautohotfix kbexchtransport kbexpertiseinter kbqfe kbhotfixserver KB951558|