thesurg3on
asked on
Exchange Mailbox Send Queue > 25
I am getting these alerts frequently and am concerned with them. What should and can I look at to track down the cause of this daily?
Information Store Queue of Messages from MTA > 25 This rule tracks the number of messages in transit from the MTA to the Exchange store. It uses the MSExchangeIS Transport Driver object and the Current Message From MSExchangeMTA counter.
I read the technet, but it does not really say, "check this out and if this is not working, then this is the reason why"
Severity: Error
Status: New
Source: MSExchangeIS Mailbox: Send Queue Size: _Total
Name: Mailbox Store: Send Queue > 25
Description: MSExchangeIS Mailbox: Send Queue Size: _Total value = 25.2. The average over last 15 samples is 25.2.
Domain: MYDOMAIN
Agent: SERVER2
Information Store Queue of Messages from MTA > 25 This rule tracks the number of messages in transit from the MTA to the Exchange store. It uses the MSExchangeIS Transport Driver object and the Current Message From MSExchangeMTA counter.
I read the technet, but it does not really say, "check this out and if this is not working, then this is the reason why"
Severity: Error
Status: New
Source: MSExchangeIS Mailbox: Send Queue Size: _Total
Name: Mailbox Store: Send Queue > 25
Description: MSExchangeIS Mailbox: Send Queue Size: _Total value = 25.2. The average over last 15 samples is 25.2.
Domain: MYDOMAIN
Agent: SERVER2
ASKER
doing a health check i got Nonpaged pool memory is crital at 113MB.
Are you getting events 2020 & 2019 in the Application Event Log too?
If you have - it sounds like your drivers are not up-to-date.
http://blogs.msdn.com/ntdebugging/archive/2006/12/18/Understanding-Pool-Consumption-and-Event-ID_3A00_--2020-or-2019.aspx
Probably worth a quick server reboot, then make sure your drivers are all up-to-date, Windows is up-to-date and Exchange is up-to-date.
If you have - it sounds like your drivers are not up-to-date.
http://blogs.msdn.com/ntdebugging/archive/2006/12/18/Understanding-Pool-Consumption-and-Event-ID_3A00_--2020-or-2019.aspx
Probably worth a quick server reboot, then make sure your drivers are all up-to-date, Windows is up-to-date and Exchange is up-to-date.
ASKER
we will fail the cluster over late. no 2020 or 2019 events. but the nic drivers are over 3 years old. we will take care of that later, but still wondering what is going on now.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
yeah, am running perfmon and giving that to MS and MSPREPORTS as we speak.
ASKER
still working on it
Lovely! - hope you get somewhere soon :-)
Alan
Alan
ASKER
yeah, going to change the MS tech in 20 minutes as this has taken
Without further comment - I would recommend a Delete WITH refund.
ASKER
thx
ASKER
mem leak thx.
Or assign me the points ! Thanks - did you identify the problem?
ASKER
yes. HP NIC Drivers.
Brilliant - thanks for the update. Glad it got resolved.
ASKER
thx for your help
No problems - anytime. Wish I could have been more specific.
http://www.microsoft.com/downloads/details.aspx?familyid=DBAB201F-4BEE-4943-AC22-E2DDBD258DF3&displaylang=en
Have you looked at the queues? If so, who is the mail from? Is it internal people, people you have never heard of or is it the postmaster?
You could be an open relay, authenticated relay, or sending out backscatter (replying with NDR reports to spammers with spoofed email addresses).