Solved

Server 2012 r2 IIS stops responding

Posted on 2016-08-25
4
21 Views
Last Modified: 2016-10-14
I have a 2012 r2 virtual server on VMware running IIS.  IIS randomly stops responding.  If I'm off site all I have to do is remote into the server and IIS starts responding so I'm not sure if it is an issue with IIS or some other issue.  Obviously the server isn't none responsive since I can remote into it.  I don't have to interact with IIS only remote into the server to get the web pages to come up.
0
Comment
Question by:bowsere
4 Comments
 
LVL 26

Expert Comment

by:Dan McFadden
ID: 41771523
2 things are possibly contributing to this situation:

1. IIS Application Pool time

What is happening is that the AppPool that supports the website, is using the default settings which allow the AppPool to be shutdown after a defined period of time, when no activity is hitting the sites.

You can turn this off by doing the following:

1. Open IIS Manager
2. Locate the Application Pool for the website in question
3. Right-click on the AppPool and select "Advanced Settings"
4. Under the Process Model section, the third setting is labeled "Idle Time-Out (minutes), the default setting is 20 minutes.  Set this to 0.  This will tell IIS to never allow the AppPool to be shut down due to being idle for too long.

The second possibility, though less likely an issue, VMWare may be suspending the Virtual Machine after being idle for too long, to conserve power and resources for other VM guest OSes.

But I would first try reconfiguring the IIS AppPool to prevent Idle Time-Outs.

Dan
0
 
LVL 76

Expert Comment

by:arnold
ID: 41771599
Does your system maintain logs, do you analyze those logs? Do you have application monitoring. Does the stopage always occur within a specific pattern, same time of the day, same time of xth day, etc.

once a pattern is determined, checking what else might be going with the back end i.e. if a database is used, what happens there during the same time frame.
0
 

Accepted Solution

by:
bowsere earned 0 total points
ID: 41775137
Thank you all for your suggestions.  After further analyzing the problem it ended up being the way our Cisco ASA firewall was handling the SSL handshake and not a problem with the server or IIS.  We were able to remove the access control rules and re-publish the website in the ASA in a different fashion and appears to have resolved the problem.
0

Featured Post

Maximize Your Threat Intelligence Reporting

Reporting is one of the most important and least talked about aspects of a world-class threat intelligence program. Here’s how to do it right.

Join & Write a Comment

When we have a dead host and we lose all connections to the ESXi, and we need to find a way to move all VMs from that dead ESXi host.
In this article, I will show you HOW TO: Create your first Windows Virtual Machine on a VMware vSphere Hypervisor 6.5 (ESXi 6.5) Host Server, the Windows OS we will install is Windows Server 2016.
Teach the user how to join ESXi hosts to Active Directory domains Open vSphere Client: Join ESXi host to AD domain: Verify ESXi computer account in AD: Configure permissions for domain user in ESXi: Test domain user login to ESXi host:
This tutorial will walk an individual through the steps necessary to join and promote the first Windows Server 2012 domain controller into an Active Directory environment running on Windows Server 2008. Determine the location of the FSMO roles by lo…

758 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

17 Experts available now in Live!

Get 1:1 Help Now