blueboxit
asked on
Messages stuck in local delivery queue after Disaster Recovery (SBS2003) Event ID 327
We recently had to completely restore an SBS2003 server from an SBS backup due to a total failure of their RAID Array. We restored the server, removed the log files from the exchange directory and then re-ran the restore with just the information stores selected. This worked a treat and we had a working server again, or so we thought. Now messages are getting stuck in the retry state in the local delivery queue of exchange. I turned up the logging and discovered the following errors....
Event Type: Warning
Event Source: MSExchangeTransport
Event Category: Exchange Store Driver
Event ID: 327
Date: 17/02/2010
Time: 11:26:41
User: N/A
Computer: BENSRV01
Description:
The following call : EcLocallyDeliverMsg to the store failed. Error code : -1605 (Message-ID <A20D104D34BA564FB476DC3BC
For more information, click http://www.microsoft.com/contentredirect.asp.
So far i've tried using ISINTEG -fix -test alltests which repaired a few errors in the table, but after remounting the store i started getting the same errors. At the moment i'm trying an offlne defrag using eseutil but i was wondering if there is anything else i can be looking at whilst this is being run?
Regards,
Simon
Event Type: Warning
Event Source: MSExchangeTransport
Event Category: Exchange Store Driver
Event ID: 327
Date: 17/02/2010
Time: 11:26:41
User: N/A
Computer: BENSRV01
Description:
The following call : EcLocallyDeliverMsg to the store failed. Error code : -1605 (Message-ID <A20D104D34BA564FB476DC3BC
For more information, click http://www.microsoft.com/contentredirect.asp.
So far i've tried using ISINTEG -fix -test alltests which repaired a few errors in the table, but after remounting the store i started getting the same errors. At the moment i'm trying an offlne defrag using eseutil but i was wondering if there is anything else i can be looking at whilst this is being run?
Regards,
Simon
Shivkumar Sharma
This issue can occur if a server-side rule on the user's Inbox that would apply to the undelivered message fails. Disable the rule(s), and see if the messages are then delivered to the Inbox. If so, the reason for the rule(s) failure needs to be diagnosed and remedied
ASKER
Would the rules need disabling on each outlook client? or can it be done from the server in some way or another? Also, is there a diagnostic logging that i can turn up to diagnose this issue?
I am talking about the server side rule which you can disable by logging in through OWA and not Outlook client
To set the diagnostic logging level for MSExchangeTransport
http://technet.microsoft.com/en-us/library/aa997825(EXCHG.65).aspx
To set the diagnostic logging level for MSExchangeTransport
http://technet.microsoft.com/en-us/library/aa997825(EXCHG.65).aspx
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Thnx for sharing it