Team, Need help on local delivery queues piled up issues on exchange server 2003. Recently one of our Exchnage server local delivery mails were piled up to 2000 and that it was released later and still we were able to see some of the old mails were located.Rebooted the server,restarted smtp services,disabled antiviru services, didnt help. We have enabled diagnostics logging on to the server (MSExchnage Transport) and below are the events and performed below activities Moved all the mailboxes to different server and recreated the database, but it still its genearting the logs with the event id 327. Event Type: Warning Event Source: MSExchangeTransport Event Category: Exchange Store Driver Event ID: 327 Date: 10/16/2010 Time: 4:06:49 PM User: N/A Computer: Description: The following call : EcLocallyDeliverMsg to the store failed. Error code : -2147221233 (Message-ID <D054F1364D20294393C308616BA94E8A025C8E8B@>). MDB : 915d2535-7dd2-4923-8334-12df79b36126. FID : . MID : . File : F:\Program Files\Exchsrvr\Mailroot\vsi 1\Queue\NTFS_b8991f4101cb6c7300001463.EML. In our environment we have single drive for all the stores and separate 1 drive for logs. Kindly let us know the solution as early as possible, we have been facing this problem from almost from 2 months.

Hi, This mught help: http://support.microsoft.com/kb/909266 Leif

Hi, Thanks for the reply. The article which you have mentioned is applicable to 2000, we are using 2003 and noticed majority of the mails are from individuals. Regards Venkat

To resolve this issue try getting this hotfix applied. http://support.microsoft.com/kb/920845 I woudl suggest to get exchange 2003 to latest sp level and post sp level.

When you get an event ID 327, there was a problem with content conversion. -2147221233 basically means "EcNotFound". What it is that wasn't found could be a message, a recipient, an attachment, or a property. KB920845 would be a good thing to check if the messages contain TNEF attachments. You could verify that by opening one of the EML files. It that KB doesn't solve your issue, you'll need to track down what it was that wasn't found. J

Hi, You can run Isinteg command to check the integrity of the database if the above KB not resolve the issue. Thanks AllenAllen Song

I would try disabling the A.V and and also relocating the VSi folder to some other drive. I would also run EXBPA to make sure all config looks goodVinod |CCNA|MCSE 2003 +Messaging|MCTS|ITIL V3|

Determine whether a corrupted recipient mailbox is causing you to experience this problem To obtain the error related information, follow these steps: Enable Information store tracing capabilities. Run the Translog utility to enable the Exchange Trace Utility (Regtrace.exe) and the debug level for MSExchangeTransport logging. 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: Click Start, click Run, type cmd in the Open box, and then click OK. At the command prompt, locate the ExchSrvr\Bin folder, type the following command, and then press ENTER: isinteg -s <<var>ServerName</var>> -fix -test alltests 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. Type Y, and then press ENTER.