Exchange 2003 messages getting stuck in Local Delivery Queue after crash

Hi Everyone,

I have an *interesting* problem...

I have a 3 node Hyper-V cluster running Server 2008 R2 Core Enterprise.  The cluster has several guest VM's loaded on a CSV that runs off of an iSCSI SAN so that I can Live Migrate them between the nodes.  A couple of days ago, the LUN with CSV volume was corrupted and I had to replace it with a failover LUN...however, that data on that LUN was several days old and when I booted the VM's, I ran into some issues.  Most of those issues have been now solved, but one significant issue remains...

One of my guest VM's is a Windows Server 2003 32-bit guest with Exchange 2003 SP1, and after being brought back online, something strange has happened with my mail.  All of my users have the ability to send mail anywhere (internal and external domains).  However, certain users are unable to receive any new mail (although they can still send mail).  When I look in the message queue for the mail server, I see messages getting piled up in the Local Delivery queue.  Trying to unfreeze them or force the connection on the queue does nothing - they just don't get delivered.  To add to that, the problem exists on users with mailboxes in different mailstores and seems to show no consistent pattern.  It is also spereading - more and more people are being affected.

Does anyone have any thoughts on this?
Who is Participating?
midnight000Connect With a Mentor Author Commented:
Just an update...

No isinteg and eseutil fixes worked.  The problem was solved by creating new DB's in each Storage Group and moving all the mailboxes from the old DB to the new DB.

Thanks for the assistance though!
Alan HardistyCo-OwnerCommented:
The problem you describe is usually as a result of mailstore corruption and the usual fix is to dismount it, repair it, defragment it and integrity check it.

To do this, please run the following:

eseutil /p

eseutil /d

isinteg -s servername -fix -test alltests
midnight000Author Commented:
The proposed solution did not work.  I worked on the issue and came up with a fix eventually.
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.