ASP.Net application recycling problem

  • Thread starter Thread starter Andriy Gnennyy
  • Start date Start date
A

Andriy Gnennyy

Hello everyone,

We have large and complex ASP.Net web application.
Eventually IIS recycles our application due to deadlock condition. The error
message in the event log looks like this:

---------------------------------------------
Event Type: Error
Event Source: ASP.NET 1.0.3705.288
Event Category: None
Event ID: 1003
Description:
aspnet_wp.exe (PID: 2356) was recycled because it was suspected to be in a
deadlocked state. It did not send any responses for pending requests in the
last 180 seconds.
---------------------------------------------

After that, typically, the application starts without any problems by first
incoming page request. But, sometimes the application doesn't restart
correctly after recycling. Each request produces the following error:

---------------------------------------------
Application crashed.
Reason :
System.Exception: System.Configuration.ConfigurationException: It is an
error to use a section registered as allowDefinition='MachineToApplication'
beyond application level. This error can be caused by a virtual directory
not being configured as an application in IIS.
(D:\InetPub\wwwroot\web.config line 25)
at System.Web.Configuration.HttpConfigurationSystem.CacheLookup(String
vpath)
---------------------------------------------

The web.config file line 25 is: <authentication mode="Windows" />
Currently we don't have any idea about the reason of such behavior. Could
anybody help with this?

Our environment:
Win 2000,
IIS 5.0,
.Net Framework 1.0,
the application resides in wwwroot,
process isolation level - Medium(pooled)

--
Andriy Gnennyy
pulsar2003@{no-spam}email.ru (Please remove {no-spam} for reply)
X-Unity Test Studio
http://x-unity.miik.com.ua/teststudio.aspx
Bring the power of unit testing to VS .NET IDE
 
Thank you for information.

But, originally the question was about the application behavior after the
aspnet_wp recycled. Time-to-time the application is unable to start after
recycling. See the exception information below. Could anybody bring the
light to the possible reason of such exception?

In addition, our application impersonate itself as domain user for several
tasks. Maybe impersonation can cause unsuccessful application restart? For
example, when the application was recycled at a moment when it works as
domain user.
 
This exception is caused by an application configuration element
which is used in a non application directory.
The problem seems to be related to the first one.
What i think may happen is that the config.web file is processed before the
application is restarted for some reason.
And when theres no application the <authentication> tag is invalid.
 
Back
Top