Solved

Exchange 2003 messages getting stuck in Local Delivery Queue after crash

Posted on 2011-02-17
3
860 Views
Last Modified: 2012-08-13
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?
0
Comment
Question by:midnight000
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 2
3 Comments
 
LVL 76

Expert Comment

by:Alan Hardisty
ID: 34922004
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
0
 

Accepted Solution

by:
midnight000 earned 0 total points
ID: 34945991
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!
0
 

Author Closing Comment

by:midnight000
ID: 34986544
The proposed solution did not work.  I worked on the issue and came up with a fix eventually.
0

Featured Post

Free Tool: IP Lookup

Get more info about an IP address or domain name, such as organization, abuse contacts and geolocation.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

This article explains in simple steps how to renew expiring Exchange Server Internal Transport Certificate.
This article lists the top 5 free OST to PST Converter Tools. These tools save a lot of time for users when they want to convert OST to PST after their exchange server is no longer available or some other critical issue with exchange server or impor…
The video tutorial explains the basics of the Exchange server Database Availability groups. The components of this video include: 1. Automatic Failover 2. Failover Clustering 3. Active Manager
This video demonstrates how to sync Microsoft Exchange Public Folders with smartphones using CodeTwo Exchange Sync and Exchange ActiveSync. To learn more about CodeTwo Exchange Sync and download the free trial, go to: http://www.codetwo.com/excha…

738 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question