• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 79
  • Last Modified:

exchange, windows server

my server went to back pressure. is process explorer good tool to check which computers or servers caused this.
  • 4
1 Solution
Scott CSenior Systems EnginerCommented:
Take a look at these 2 articles.

From <https://technet.microsoft.com/en-us/library/bb201658(v=exchg.141).aspx
From <https://technet.microsoft.com/en-us/library/bb201658.aspx

Probably not process explorer as it's a shortage of resources that cause back pressure.

Connections are being refused due to lack of resources.  Check disk space first.
pramod1Author Commented:
it has enough disk space free
pramod1Author Commented:
I need to know the connections which could cause high lsass.exe and in turn back pressure
Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

pramod1Author Commented:
I have physical memory : 10gb, virtual : average virtual :9.6
IvanSystem EngineerCommented:

as ScottCha said, those 2 articles as good one.

By default, the high level of memory utilization by all processes is 94 percent of total physical memory.
9.6 out of 10Gb is 96%. That means that there is high level of memory utilization and message dehydration is occurring.

pramod1Author Commented:
yes I see that in error, but as per logs I see lot of active sync connections at that time, is that the primary issue

Featured Post

NFR key for Veeam Agent for Linux

Veeam is happy to provide a free NFR license for one year.  It allows for the non‑production use and valid for five workstations and two servers. Veeam Agent for Linux is a simple backup tool for your Linux installations, both on‑premises and in the public cloud.

  • 4
Tackle projects and never again get stuck behind a technical roadblock.
Join Now