locked
Mysterious IIS Application Reset RRS feed

  • Question

  • User2020527074 posted

    I'm having a weird problem where my ASP.Net application resets after doing some specific actions on my website. After adding some logging in Application_End(), I see that the shutdown reason is due to "ConfigurationChange". I obtained this from System.Web.Hosting.HostingEnvironment.ShutdownReason. However, I have looked and looked and no config files seem to be changing on my web server. There is no anti-virus running on the server. We are using Windows Server 2012 R2, IIS version  6.2, .NET version 4.5.


    Also, yes we do have patch KB3052480 installed. Any help would be very much appreciated. Thanks. 

    Wednesday, October 19, 2016 7:03 PM

All replies

  • User-460007017 posted

    Hi Hamoush,

    The problem may be caused by CPU limit action or idle time out. Please try to disable these configurations in IIS manager->application pool->set idle time out to 0.

    If you enabled generate recycle event log entry, you could find the changeconfiguration record in event viewer.

    Besides, you may use following code with System.Web.ApplicationShutdownReason shutdownReason to get the detailed error message.

    http://mitchelsellers.com/blogs/2007/03/15/logging-aspnet-application-restarts.aspx

    Best Regards,

    Yuk Ding

    Thursday, October 20, 2016 7:14 AM
  • User2020527074 posted

    Hi Yuk, thanks for looking into this for me. 

    Our CPU limit was already set to 0. I tried setting the idle timeout to 0 as well but still get the same problem. I do not think it's a timeout issue as it happens only if the first user to log on after the server has been restarted carries out a certain action on the website. After the problem happens once, it doesn't happen again unless the entire server is restarted (even if a user carries out the same action again). 

    Also, I do not see any recycle event log entries when this problem occurs. Our problem is with application restarts, not application pool recycles. The W3WP.exe process stays the same. This should be the reason why we do not see any recycle log entries.

    Thursday, October 20, 2016 4:03 PM
  • User690216013 posted

    No matter what file has changed, it is .NET, so you can always debug it in the proper way,

    https://blogs.msdn.microsoft.com/rodneyviana/2015/03/12/the-strange-case-of-the-application-pool-recycling-causing-high-cpu/

    If you are not capable of following the steps, open a support case via http://support.microsoft.com 

    Friday, October 21, 2016 3:29 AM