FIX: Event ID 2262 is logged in the Application event log when an ASP.NET 2.0 Web application becomes unresponsive

Article translations Article translations
Article ID: 974165 - View products that this article applies to.
Expand all | Collapse all

On This Page


When you run a Microsoft ASP.NET 2.0 Web application on a computer that is running Windows XP or Windows Server 2003, the application becomes unresponsive. Additionally, an event that resembles the following is logged in the Application event log:

Event Type: Warning
Event Source: W3SVC-WP Event Category: None
Event ID: 2262
Description: ISAPI 'C:\Windows\Microsoft.NET\Framework\v2.0.50727\aspnet_isapi.dll' reported itself as unhealthy for the following reason: 'Deadlock detected'.

This problem occurs when the Web application has a control that contains multiple duplicate properties. For an example of a control that contains multiple duplicate properties, refer to the "MORE INFORMATION" section.

IMPORTANT: There are many possible different ways that a deadlock can occur in an ASP.NET web application that will result in the 'Deadlock Detected' error message above. This article focuses on one specific scenario that will result in a deadlock, and the hotfix introduced below will only resolve this one specific scenario. If you are running into a deadlock scenario, please check the File Information section below and verify that your versions of the ASP.NET binaries are higher than those listed in the File Information section. If your file versions are higher than those listed below, you do not need to install this hotfix. Rather, you should troubleshoot your deadlock scenario from a general perspective by following the instructions in this knowledge base article:

How to generate a dump file when ASP.NET deadlocks in IIS 6.0


This problem occurs because multiple threads try to access Web browser properties at the same time. Therefore, a deadlock occurs.


Hotfix information

A supported hotfix is now available from Microsoft. However, it is intended to correct only the problem that is described in this article. Apply it only 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 2.0 service pack that contains this hotfix.

To resolve this problem immediately, contact Microsoft Customer Support Services to obtain the hotfix. For a complete list of Microsoft Customer Support Services telephone numbers and information about support costs, visit the following Microsoft Web site:
Note 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.


You must have either the Microsoft .NET Framework 2.0 Service Pack 2 (SP2) or the Microsoft .NET Framework 3.5 Service Pack 1 (SP1) installed to apply this hotfix.

Restart requirement

You have to restart the computer after you apply this hotfix if any of the affected files are being used when you install it. However, you do not have to restart the system if you close all ASP.NET Web sites before you install this hotfix.

Hotfix replacement information

This hotfix does not replace any other hotfixes.

File information

The global version of this hotfix has the file attributes (or later file attributes) 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 item in Control Panel.
Windows XP and Windows Server 2003 x86-based version
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatform
Windows XP and Windows Server 2003 x64-based version
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatform
Windows Server 2003, IA64-based version
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatform


To work around this problem, remove the duplicate properties.


Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.


The following is an example of a control that contains multiple duplicate properties:
<asp:gridview id="GridView1" runat="server" 
                    PageSize="100" PagerSettings-Mode="Numeric" 
                    PagerStyle-BorderStyle="None" PagerStyle-BorderColor="Navy" 
                    PagerStyle-HorizontalAlign="Right" PagerSettings-PageButtonCount="2" 
			<PagerStyle HorizontalAlign="Left" BorderColor="Navy" BorderStyle="None"></PagerStyle>
        		<PagerSettings PageButtonCount="2"></PagerSettings>
Note The PagerSettings property and the PagerStyle property are duplicated because they are set in the gridview tag and in their own tags.

For more information about ASP.NET Web server controls and browser capabilities, visit the following Microsoft Developer Network (MSDN) Web site:
For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:
824684 Description of the standard terminology that is used to describe Microsoft software updates


Article ID: 974165 - Last Review: April 13, 2012 - Revision: 4.0
  • Microsoft .NET Framework 3.5 Service Pack 1
  • Microsoft .NET Framework 2.0 Service Pack 2
  • Microsoft ASP.NET 2.0
kbexpertiseadvanced kbsurveynew kbqfe KB974165

Give Feedback


Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from