Solved

Microsoft Exchange / Analysing backpressure issue

Posted on 2014-02-12
5
225 Views
Last Modified: 2014-02-14
Hi,

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
Simon
0
Comment
Question by:Psymonious
  • 2
  • 2
5 Comments
 
LVL 7

Expert Comment

by:jimmithakkar
ID: 39855691
Hi,

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

Expert Comment

by:chriskelk
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.
0
 
LVL 1

Author Comment

by:Psymonious
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?
0
 
LVL 3

Accepted Solution

by:
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.
0
 
LVL 1

Author Comment

by:Psymonious
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.
0

Featured Post

PRTG Network Monitor: Intuitive Network Monitoring

Network Monitoring is essential to ensure that computer systems and network devices are running. Use PRTG to monitor LANs, servers, websites, applications and devices, bandwidth, virtual environments, remote systems, IoT, and many more. PRTG is easy to set up & use.

Question has a verified solution.

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

Suggested Solutions

Title # Comments Views Activity
Office 365 & Microsoft Azure 8 63
IronPort on cloud MX recored 9 25
exchange, outlook 4 21
SBS 2011 Ran SharePoint Config Wizard and Exchange ActiveSync failed. 5 27
This article explains in simple steps how to renew expiring Exchange Server Internal Transport Certificate.
This article aims to explain the working of CircularLogArchiver. This tool was designed to solve the buildup of log file in cases where systems do not support circular logging or where circular logging is not enabled
In this video we show how to create a Shared Mailbox in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.: First we need to log into the Exchange Admin Center. Navigate to the Recipients >> Sha…
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…

862 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

Need Help in Real-Time?

Connect with top rated Experts

27 Experts available now in Live!

Get 1:1 Help Now