?
Solved

exchange, windows server

Posted on 2016-07-25
6
Medium Priority
?
74 Views
Last Modified: 2016-07-25
my server went to back pressure. is process explorer good tool to check which computers or servers caused this.
0
Comment
Question by:pramod1
[X]
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
  • 4
6 Comments
 
LVL 31

Accepted Solution

by:
Scott C earned 2000 total points
ID: 41727750
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.
1
 

Author Comment

by:pramod1
ID: 41727751
it has enough disk space free
0
 

Author Comment

by:pramod1
ID: 41727753
I need to know the connections which could cause high lsass.exe and in turn back pressure
0
Office 365 Training for IT Pros

Learn how to provision tenants, synchronize on-premise Active Directory, implement Single Sign-On, customize Office deployment, and protect your organization with eDiscovery and DLP policies.  Only from Platform Scholar.

 

Author Comment

by:pramod1
ID: 41727759
I have physical memory : 10gb, virtual : average virtual :9.6
0
 
LVL 17

Expert Comment

by:Ivan
ID: 41727771
Hi,

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.

Regards,
Ivan.
0
 

Author Comment

by:pramod1
ID: 41727781
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
0

Featured Post

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.

Question has a verified solution.

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

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…
A couple of months ago we ran into an issue that necessitated re-creating our Edge Subscriptions. However, when we attempted to execute the command: New-EdgeSubscription -filename C:\NewEdgeSub_01.xml we received an error indicating that the LDAP se…
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…
Sometimes it takes a new vantage point, apart from our everyday security practices, to truly see our Active Directory (AD) vulnerabilities. We get used to implementing the same techniques and checking the same areas for a breach. This pattern can re…
Suggested Courses
Course of the Month15 days, 15 hours left to enroll

741 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