Avatar of regsamp
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.
ExchangeWindows Server 2003

Avatar of undefined
Last Comment
ckratsch

8/22/2022 - Mon
ASKER CERTIFIED SOLUTION
Alan Hardisty

Log in or sign up to see answer
Become an EE member today7-DAY FREE TRIAL
Members can start a 7-Day Free trial then enjoy unlimited access to the platform
Sign up - Free for 7 days
or
Learn why we charge membership fees
We get it - no one likes a content blocker. Take one extra minute and find out why we block content.
Not exactly the question you had in mind?
Sign up for an EE membership and get your own personalized solution. With an EE membership, you can ask unlimited troubleshooting, research, or opinion questions.
ask a question
regsamp

ASKER
Yes, it is.  Thank you.
ckratsch

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

http://support.microsoft.com/kb/924206

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.
regsamp

ASKER
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.
Experts Exchange has (a) saved my job multiple times, (b) saved me hours, days, and even weeks of work, and often (c) makes me look like a superhero! This place is MAGIC!
Walt Forbes
ckratsch

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.