Microsoft Exchange / Analysing backpressure issue

Posted on 2014-02-12
Last Modified: 2014-02-14

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
Question by:Psymonious
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
  • 2

Expert Comment

ID: 39855691

that has been caused by a lack of disk space. please check disk space,

Expert Comment

ID: 39858774
Are there any events in the application log?  Backpressure creates events in the 15004-7 range, which should help pin the problem down.

Author Comment

ID: 39858864
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?

Accepted Solution

chriskelk earned 500 total points
ID: 39858868
Read more of the article I linked earlier, it includes a list of options available including all the thresholds that backpressure uses.

Author Comment

ID: 39858922
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.

Featured Post

Why You Need a DevOps Toolchain

IT needs to deliver services with more agility and velocity. IT must roll out application features and innovations faster to keep up with customer demands, which is where a DevOps toolchain steps in. View the infographic to see why you need a DevOps toolchain.

Question has a verified solution.

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

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…
This article will help to fix the below errors for MS Exchange Server 2013 I. Certificate error "name on the security certificate is invalid or does not match the name of the site" II. Out of Office not working III. Make Internal URLs and Externa…
The basic steps you have just learned will be implemented in this video. The basic steps are shown to configure an Exchange DAG in a live working Exchange Server Environment and manage the same (Exchange Server 2010 Software is used in a Windows Ser…
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:…

724 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