Consider the following scenario:

•	An application is built by using the Microsoft .NET Framework 2.0.
•	The application runs in the Microsoft .NET Framework 2.0.
•	The application runs under a user account context.
•	No user profile is associated with the user account context.

In this scenario, the application may crash, or you may receive an access violation error message. If you debug the crash, you find an access violation in the mscorwks!SecurityConfig::GetCacheEntry function.

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 1Error message 2Notes

•	Error message 2 immediately follows error message 1.
•	This problem occurs with ASP.NET 2.0 applications. This problem may occur with other types of applications that run under non-interactive accounts, such as Windows services.

Additionally, in Microsoft Windows SharePoint Services 3.0 or in Microsoft Office SharePoint Server 2007, you may be prompted for authentication when you connect to the Site Usage Report page of a Web site to view the usage data for that Web site. Then, you may recieve the following error message:The following event is logged in the event log:

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)

Back to the top

This problem occurs when a null reference is in the user policy cache.

Back to the top

Hotfix information

A supported hotfix is now available from Microsoft. But the hotfix is intended only to correct the problem that is described in this article. Apply this hotfix 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 Visual Studio 2005 service pack that contains this hotfix. To resolve this problem immediately, visit the following Microsoft Web site:

Prerequisites

To apply this hotfix, you must have the .NET Framework 2.0 installed on the computer.

Restart requirement

You must restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace any other hotfixes.

File information

The 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.

File name	File version	File size	Date	Time	Platform
Mscordacwks.dll	2.0.50727.63	800,256	24-Jan-2006	11:16	x86
Mscorlib.dll	2.0.50727.63	4,308,992	24-Jan-2006	11:16	x86
Mscorwks.dll	2.0.50727.63	5,616,640	24-Jan-2006	11:16	x86
Sos.dll	2.0.50727.63	377,344	24-Jan-2006	11:16	x86

Back to the top

For more information, click the following article number to view the article in the Microsoft Knowledge Base:

Back to the top

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.

Back to the top

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

Back to the top