Some inbound mail stays in Local Delivery queue - EcLocallyDeliverMsg
I stumbled across an interesting problem yesterday in an organization that is migrating from Exchange 5.5 to Exchange 2003. Inbound mail all still flows in to their organization via the Internet Mail Service. Some e-mail is delivered to the E2K3 recipients just fine, but some mail stays in the Local Delivery queue. The E2K3 SP2 server is running W2K3 with all publicly available / downloadable fixes.
After cranking up the Exchange Store Driver diagnostics logging up to Maximum, we saw some interesting messages:
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 :
-2147024809 (Message-ID xxxx). MDB : xxxx. FID : xxxx
A quick search of the error code (2147024809) yielded a brand new KB article and a hotfix (whew!). See KB 934450 "You experience problems after you apply hotfix 930241 or hotfix 931978 to a server that is running Exchange Server 2003"
5 Comments:
More info. from below link:
http://msexchangeteam.com/archive/2007/05/09/438525.aspx
sorry - above link is not same problem although it's simliar problem.
Did this solution work for you? I'm having a similar problem converting from 5.5 to 2003. However I did not install hotfix 934450.
Yep, this solution fixed us right up.
Soon after we installed the 931832 patch, we also experienced mail flow issues where messages would not be delivered and were being held in the local delivery queue.
Installing patch 934450 did resolve this problem, however we now have a different mail flow issue whereby emails are intermittently being delivered to the journal mailbox and not to the intended recipient. When this happens we have 2 entries from the smtp store driver delivering to our journal mailbox when viewing the message in message tracking centre. We'd expect to see only 1 entry for the journal mailbox and 1 entry for the recipient mailbox from the smtp store driver.
Has anyone experienced the same problem with patch 934450?
Our store.exe version is currently 6.5.7653.2. Is there a patch / hotfix which supercedes 934450?
Post a Comment
<< Home