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.

E-mail messages that you send to a distribution list remain in the local delivery queue of Exchange 2000 Server server


View products that this article applies to.

Symptoms

You try to send e-mail messages to a distribution list. However, the e-mail messages remain in the local delivery queue of the server that is running Microsoft Exchange 2000 Server.

↑ Back to the top


Cause

This problem occurs because one of the recipients has a corrupted mailbox.

↑ Back to the top


Resolution

To resolve this problem, you must first review any error related information to determine whether a corrupted recipient mailbox is causing you to experience this problem. Then, you remove the corrupted recipient mailbox.

Determine whether a corrupted recipient mailbox is causing you to experience this problem

To obtain the error related information, follow these steps:
  1. Enable Information store tracing capabilities.
  2. Run the Translog utility to enable the Exchange Trace Utility (Regtrace.exe) and the debug level for MSExchangeTransport logging.
  3. Force the connection on the local delivery queue on the Exchange 2000 Server server.
After you follow these steps, you may receive the following error information:
  • The Application log may contain the following event ID:
    Event ID: 327 
    Category: Exchange Store Driver 
    Source: MSExchangeTransport 
    Type: Warning 
    Description: 
    The following call: EcOpenItemForLocalDelivery to the store failed. 
    Error code: -1601. MDB : . FID : . MID : . File : . 
  • The Trace.atf file may contain the following errors:
    Input DN = CN=USER NAME,CN=Users,DC=company,DC=com 
    Output DN = /DC=COM/DC=PUGHCOMPANY/CN=USERS/CN=USER NAME 
    EcLocallyDeliverMsg failed with ec : -2147221233 
    m_pMdbLogon->HrDoLocalDelivery failed with hr : 0x80040158 
    pRecips->GetProperty failed with hr : 0x800300fd
    EcLocallyDeliverMsg failed with ec : -2147221240 
    m_pMdbLogon->HrDoLocalDelivery failed with hr : 0xc0040152 
  • The Store.log file from the store tracing may contain the following errors:
    00000A14 [2004-07-19 10:10:20] TAG 74:  EcLocallyDeliverMsg: 
    ec=ecNotFound-MAPI_E_NOT_FOUND (0x8004010f), Failed to deliver msg MID=0-0, to 
    mailbox/PF /DC=COM/DC=COMPANY/CN=USERS/CN=USER NAME
    00000A14 [2004-07-19 10:10:20] TAG 74:  EcLocallyDeliverMsg: OMSG is invlalid
    00000A14 [2004-07-19 10:10:20] TAG 3:  Error ecInvalidObject-MAPI_E_INVALID_OBJECT 
    (0x80040108) in EcLocallyDeliverMsg
All three of these errors indicate that a mailbox is corrupted. To test these errors, remove the user who is associated with the corrupted mailbox from the distribution list. Then, send a test e-mail message to the distribution list. If the e-mail message is not delivered, this confirms that mailbox is corrupted. After you determine that the mailbox is corrupted, you must remove the mailbox.

Remove the corrupted mailbox

To remove the corrupted mailbox, use one of the following methods:
  • Move the corrupted mailbox to another mailbox store.

    Note The corruption may cause the move mailbox operation to fail.
  • Export the mailbox data to a personal folders (.pst) file, delete the original mailbox, create a new mailbox, and then re-import the mailbox data.
  • Run the isinteg -fix command against the mailbox store of the corrupted mailbox. To do this, follow these steps:
    1. Click Start, click Run, type cmd in the Open box, and then click OK.
    2. At the command prompt, locate the ExchSrvr\Bin folder, type the following command, and then press ENTER:
      isinteg -s <ServerName> -fix -test alltests
    3. Type the number of the affected mailbox store, and then press ENTER.

      Note The affected mailbox is now offline. The mailbox must be offline before you run the isinteg -fix command.
    4. Type Y, and then press ENTER.

↑ Back to the top


Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

↑ Back to the top


Keywords: KB909266, kbprb, kbtshoot

↑ Back to the top

Article Info
Article ID : 909266
Revision : 4
Created on : 10/28/2006
Published on : 10/28/2006
Exists online : False
Views : 184