Microsoft Exchange / Analysing backpressure issue


We are migrating Exchange 2010 to Exchange 2013.
The mailflow still goes through the old Exchange 2010 and via internal relay to the new Exchange 2013 servers

Yesterday i saw that almost every email that i can see in this queue gets delay with
"452 4.3.1 Insufficient system resources"

I immediately thought about "Back Pressure" and searched for entries in the EventLog.
After i couldn't find anything i disabled back pressure in the "edgetransport.exe.config" for some time, to proof that the issue is caused by that.

During the disabled state i had no delays or messages with that error in the queue, so i'm pretty sure that the issue is caused by back pressure.

My problem now is that i don't have any idea how to find out which one of the back pressure thresholds is causing the issue.

Any ideas how i can deeper analyse this issue, to find out what the exact reason is?

Thanks in advance
Who is Participating?
chriskelkConnect With a Mentor Commented:
Read more of the article I linked earlier, it includes a list of options available including all the thresholds that backpressure uses.

that has been caused by a lack of disk space. please check disk space,
Are there any events in the application log?  Backpressure creates events in the 15004-7 range, which should help pin the problem down.
PsymoniousAuthor Commented:
I checked the "edgetransport.exe.config" but i cannot find the limits that are set.
Do you know how the limits are set by default?
PsymoniousAuthor Commented:
Sorry, for the post in between, i had a problem with refreshing this site.
In the meantime i found a configuration failure on the second cluster node that caused the back pressure issue.
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.