Article ID: 328267 - View products that this article applies to.
This article was previously published under Q328267
This article has been archived. It is offered "as is" and will no longer be updated.
Occasionally, slow writes to a client cause Aspnet_wp to recycle on false deadlocks. When this occurs, the following event appears in the Application event log:
Event Type: Error Event Source: ASP.NET 1.0.3705.0 Event Category: None Event ID: 1003 Date: 4/24/2002 Time: 6:18:23 PM User: N/A Computer: <ComputerName> Description: aspnet_wp.exe (PID: <xxx>) 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.
This behavior occurs if the ASP.NET worker process has been idle for the time that is specified for the responseDeadlockInterval configuration setting in the Machine.config file. This causes the deadlock detection mechanism in ASP.NET to recycle Aspnet_wp.exe. A slow write to the client may take longer than the value of responseDeadlockInterval.
A supported hotfix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Only apply it to systems that are experiencing this specific problem. This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next .NET Framework service pack that contains this hotfix.
To resolve this problem immediately, contact Microsoft Product Support Services to obtain the hotfix. For a complete list of Microsoft Product Support Services telephone numbers and information about support costs, visit the following Microsoft Web site:
http://support.microsoft.com/contactus/?ws=supportNote In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question. The English version of this fix has the file attributes (or later) that are listed in the following table. The dates and times for these files are listed in coordinated universal time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.
Date Time Version Size File name ------------------------------------------------------------------ 20-Sep-2002 17:49 1.0.3705.360 196,608 Aspnet_isapi.dll 20-Sep-2002 17:49 19,332 Aspnet_perf.ini 20-Sep-2002 17:49 1.0.3705.360 24,576 Aspnet_regiis.exe 20-Sep-2002 17:49 1.0.3705.360 28,672 Aspnet_wp.exe 20-Sep-2002 17:49 15 Smartnav.htm 20-Sep-2002 17:49 8,800 Smartnav.js 20-Sep-2002 17:49 7,003 Smartnavie5.js 20-Sep-2002 17:49 1.0.3705.360 1,187,840 System.web.dll
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
Article ID: 328267 - Last Review: October 25, 2013 - Revision: 4.0