Link to home
Start Free TrialLog in
Avatar of regsamp

asked on

Exchange server queue size keeps expanding

Our Exchange Server 2003 queue size keeps expanding and is currently up to 13976.  E-mail is intermittent and our virus software is disabled and we cannot activate it.  Any assistance offered would be greatly appreciated.
Avatar of Alan Hardisty
Alan Hardisty
Flag of United Kingdom of Great Britain and Northern Ireland image

Link to home
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of regsamp


Yes, it is.  Thank you.
I had an issue exactly like this which ended up being caused by a corrupt message store. The store was mounted in ESM, but the local delivery queue wouldn't do anything (to mailboxes in any store) until the damaged store was dismounted. Even isinteg repair on that DB didn't resolve, and we ended up having to leave it down and recover from backup.

In order to determine the root cause in my case, I was instructed to do the following:

* In ESM, right click the server and go to Properties > Diagnostics Logging. Increase logging for "MSExchangeTransport" to Maximum.
* Look for Event ID 327 in the Application Event log (it's a Warning event).
* Resolve the GUID listed in event 327 with the SystemMailbox{GUID} account in Active Directory to locate the suspect database.
* Take that database offline and repair it using isinteg, then offline defrag with eseutil

If you take the DB offline and your mail flow suddenly returns, you know you've found the problem. If you can stand to leave the DB up (no mail flow) and move mailboxes off of it and into another (new, empty) database, do that to avoid data loss.
Avatar of regsamp


It looks like it was an attack.  I followed several of the steps in the article and we are back working.  Thank you.  Thank you also CK.
Good to hear. I know my situation was kind of a longshot, but I figured it was worth mentioning, either for your purposes, or for someone else who happens across this thread in the future.