Geek Answers Handbook

What can cause an IIS application to reset?

I track my site using the healthMonitoring section. I see a message ...

Event code: 1002 Event message: Application is shutting down. Reason: Hosting environment is shutting down. Event time: 8/8/2011 3:29:59 PM Event time (UTC): 8/8/2011 8:29:59 PM Event ID: 6879adf29cdc403ba8ad2e5694b6cee0 Event sequence: 730 Event occurrence: 1 Event detail code: 50002

I am having trouble determining why it is closing. My application pool is set to reset every 24 hours. My web.config sessions expire after 4 hours (this should not affect the termination of the application). I saw that in some messages it was mentioned that the system health parameters can be reset for the application, but I do not see any specific settings that would do this. In addition, I noticed this problem before adding the healthMonitoring section.

Just for reference, this is how he reads ...

  <healthMonitoring> <bufferModes> <add name="Critical Notification" maxBufferSize="100" maxFlushSize="20" urgentFlushThreshold="1" regularFlushInterval="Infinite" urgentFlushInterval="00:01:00" maxBufferThreads="1" /> <add name="Notification" maxBufferSize="300" maxFlushSize="20" urgentFlushThreshold="1" regularFlushInterval="Infinite" urgentFlushInterval="00:01:00" maxBufferThreads="1" /> <add name="Analysis" maxBufferSize="1000" maxFlushSize="100" urgentFlushThreshold="100" regularFlushInterval="00:05:00" urgentFlushInterval="00:01:00" maxBufferThreads="1" /> <add name="Logging" maxBufferSize="1000" maxFlushSize="200" urgentFlushThreshold="800" regularFlushInterval="00:30:00" urgentFlushInterval="00:05:00" maxBufferThreads="1" /> </bufferModes> <providers> <add name="EventLogProvider" type="System.Web.Management.EventLogWebEventProvider,System.Web,Version=4.0.0.0,Culture=neutral,PublicKeyToken=b03f5f7f11d50a3a" /> <add connectionStringName="LocalSqlServer" maxEventDetailsLength="1073741823" buffer="false" bufferMode="Notification" name="SqlWebEventProvider" type="System.Web.Management.SqlWebEventProvider,System.Web,Version=4.0.0.0,Culture=neutral,PublicKeyToken=b03f5f7f11d50a3a" /> <add name="WmiWebEventProvider" type="System.Web.Management.WmiWebEventProvider,System.Web,Version=4.0.0.0,Culture=neutral,PublicKeyToken=b03f5f7f11d50a3a" /> </providers> <profiles> <add name="Default" minInstances="1" maxLimit="Infinite" minInterval="00:01:00" custom="" /> <add name="Critical" minInstances="1" maxLimit="Infinite" minInterval="00:00:00" custom="" /> </profiles> <rules> <add name="All Errors Default" eventName="All Errors" provider="EventLogProvider" profile="Default" minInstances="1" maxLimit="Infinite" minInterval="00:01:00" custom="" /> <add name="Failure Audits Default" eventName="Failure Audits" provider="EventLogProvider" profile="Default" minInstances="1" maxLimit="Infinite" minInterval="00:01:00" custom="" /> <add name="Application Lifetime Events Default" eventName="Application Lifetime Events" provider="EventLogProvider" profile="Default" minInstances="1" maxLimit="Infinite" minInterval="00:01:00" custom="" /> </rules> <eventMappings> <add name="All Events" type="System.Web.Management.WebBaseEvent,System.Web,Version=4.0.0.0,Culture=neutral,PublicKeyToken=b03f5f7f11d50a3a" startEventCode="0" endEventCode="2147483647" /> <add name="Heartbeats" type="System.Web.Management.WebHeartbeatEvent,System.Web,Version=4.0.0.0,Culture=neutral,PublicKeyToken=b03f5f7f11d50a3a" startEventCode="0" endEventCode="2147483647" /> <add name="Application Lifetime Events" type="System.Web.Management.WebApplicationLifetimeEvent,System.Web,Version=4.0.0.0,Culture=neutral,PublicKeyToken=b03f5f7f11d50a3a" startEventCode="0" endEventCode="2147483647" /> <add name="Request Processing Events" type="System.Web.Management.WebRequestEvent,System.Web,Version=4.0.0.0,Culture=neutral,PublicKeyToken=b03f5f7f11d50a3a" startEventCode="0" endEventCode="2147483647" /> <add name="All Errors" type="System.Web.Management.WebBaseErrorEvent,System.Web,Version=4.0.0.0,Culture=neutral,PublicKeyToken=b03f5f7f11d50a3a" startEventCode="0" endEventCode="2147483647" /> <add name="Infrastructure Errors" type="System.Web.Management.WebErrorEvent,System.Web,Version=4.0.0.0,Culture=neutral,PublicKeyToken=b03f5f7f11d50a3a" startEventCode="0" endEventCode="2147483647" /> <add name="Request Processing Errors" type="System.Web.Management.WebRequestErrorEvent,System.Web,Version=4.0.0.0,Culture=neutral,PublicKeyToken=b03f5f7f11d50a3a" startEventCode="0" endEventCode="2147483647" /> <add name="All Audits" type="System.Web.Management.WebAuditEvent,System.Web,Version=4.0.0.0,Culture=neutral,PublicKeyToken=b03f5f7f11d50a3a" startEventCode="0" endEventCode="2147483647" /> <add name="Failure Audits" type="System.Web.Management.WebFailureAuditEvent,System.Web,Version=4.0.0.0,Culture=neutral,PublicKeyToken=b03f5f7f11d50a3a" startEventCode="0" endEventCode="2147483647" /> <add name="Success Audits" type="System.Web.Management.WebSuccessAuditEvent,System.Web,Version=4.0.0.0,Culture=neutral,PublicKeyToken=b03f5f7f11d50a3a" startEventCode="0" endEventCode="2147483647" /> </eventMappings> </healthMonitoring>

What can cause my application to reset?

Thanks!

+4
source share
3 answers

IIS can reset / restart for many reasons.
from Tess Ferrandes blog

  • Changed Machine.Config, Web.Config or Global.asax options
  • Changed the bin directory or its contents
  • The number of repeated compilations (aspx, ascx or asax) exceeds the limit specified by the machine.config or web.config parameter (by default, this value is 15)
  • The physical path to the virtual directory has been changed
  • CAS policy changed
  • The web service restarts.
  • (2.0 only) Applications Sub-directories deleted

IIS will shut down your application if it is inactive (the default is 20 minutes without activity), consuming too much memory or processor time.
Also, antivirus programs running on the web server are accused of reselling iis, I guess, by touching any of the files / directories mentioned above.

+8
source

I had the same problems and started looking in other server logs to see if something else happened while it was being processed.

in the System event logs I found this:

A workflow with process identifier "6600" serving the application pool "Version 1.2" requested processing because the workflow reached its allowed processing time.

source was: was

(Windows Activation Service)

I know that the reasons may be different, but for future links you should also look at other magazines.

+3
source

The amount of memory used may have set limits that will lead to a reboot of the application pool, but I'm not sure if this gives the exact message you receive. See Disposal in the advanced application pool settings in IIS Manager.

+2
source

More articles:


All Articles