Select the product you need help with
- Internet Explorer
- Windows Phone
- More products
HOTFIX: A .NET Framework 2.0 application that runs under a user account context when no user profile is associated with the user account context may crash, or you may receive an access violation error message
Article ID: 913384 - View products that this article applies to.
Consider the following scenario:
If you experience this problem in a Microsoft ASP.NET application, you receive error messages in the event log that are similar to the following:
Error message 1
Error message 2
Event ID : 1023
Raw Event ID : 1023
Record Nr. : 14
Category : None
Source : .NET Runtime
Message : NET Runtime version 2.0.50727.42 - Fatal Execution Engine Error (7A05E2B3) (80131506)
Event ID : 1000
Raw Event ID : 1000
Record Nr. : 15
Category : None
Source : .NET Runtime 2.0
Error Reporting Type : Error
Message : Faulting application w3wp.exe, version 6.0.3790.1830, stamp 42435be1, faulting module mscorwks.dll, version 2.0.50727.42, stamp 4333e7ec, debug? 0, fault address 0x000e9f96.
The following event is logged in the event log:
The request failed with HTTP status 401: Access Denied
Event ID : 1023
This problem occurs when a null reference is in the user policy cache.
A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.
To download this hotfix from the MSDN Code Gallery, visit the following Microsoft Web site:
Note The MSDN Code Gallery displays the languages for which the hotfix is available. If you do not see your language listed, it is because the Code Gallery resource page is not available for that language.
Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site:
PrerequisitesTo apply this hotfix, you must have the .NET Framework 2.0 installed on the computer.
Restart requirementYou must restart the computer after you apply this hotfix.
Hotfix replacement informationThis hotfix does not replace any other hotfixes.
File informationThe English 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.
Collapse this tableExpand this table
For more information, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/824684/ )Description of the standard terminology that is used to describe Microsoft software updates
When the common language runtime (CLR) starts, the CLR verifies that the user profile exists. If the user profile does not exist, a null reference is put in the user policy cache. If the user profile is created during policy resolution, the CLR tries to remove the reference to the null reference in the user policy cache. When the CLR cannot remove the reference to the null reference in the user policy cache, the .NET Framework 2.0 crashes.
Microsoft has confirmed that this is a bug in the Microsoft products that are listed in the "Applies to" section.