Microsoft KB Archive/934839

From BetaArchive Wiki

Article ID: 934839

Article Last Modified on 12/3/2007



APPLIES TO

  • Microsoft ASP.NET 2.0
  • Microsoft .NET Framework 2.0



SYMPTOMS

When you browse a Microsoft .NET Framework 2.0 ASP.NET Web application, you may receive one of the following exceptions:

Exception 1


Exception type: FileNotFoundException Exception message: Could not load file or assembly 'App_Web_-e9dbmaj, Version=0.0.0.0, Culture=neutral, PublicKeyToken=null' or one of its dependencies. The system cannot find the file specified.

Exception 2


Compiler Error Message: CS0006: Metadata file 'C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\Temporary ASP.NET Files\cms.web\44e73607\b028acb3\App_global.asax.fakktchx.dll' could not be found

RESOLUTION

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, visit the following Microsoft Web site:

Prerequisites

You must have the .NET Framework 2.0 installed before you apply this hotfix.

Restart requirement

You do not have to restart your 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.

Microsoft .NET Framework 2.0, 32-bit versions
File name File version File size Date Time Platform
Aspnet_wp.exe 2.0.50727.819 32,600 15-Mar-2007 10:22 x86
System.web.dll 2.0.50727.819 5,156,864 15-Mar-2007 10:23 x86
Webengine.dll 2.0.50727.819 406,016 15-Mar-2007 10:22 x86
Microsoft .NET Framework 2.0, 64-bit versions
File name File version File size Date Time Platform
Aspnet_wp.exe 2.0.50727.819 44,376 15-Mar-2007 05:33 x64
System.web.dll 2.0.50727.819 5,087,232 15-Mar-2007 05:33 x64
Webengine.dll 2.0.50727.819 710,144 15-Mar-2007 02:23 x64
Aspnet_wp.exe 2.0.50727.819 32,600 15-Mar-2007 10:22 x86
System.web.dll 2.0.50727.819 5,156,864 15-Mar-2007 10:23 x86
Webengine.dll 2.0.50727.819 406,016 15-Mar-2007 10:22 x86
Microsoft .NET Framework 2.0, Itanium-based versions
File name File version File size Date Time Platform
Aspnet_wp.exe 2.0.50727.819 83,288 15-Mar-2007 06:22 IA-64
System.web.dll 2.0.50727.819 4,710,400 15-Mar-2007 06:22 IA-64
Webengine.dll 2.0.50727.819 1,181,696 15-Mar-2007 02:25 IA-64
Aspnet_wp.exe 2.0.50727.819 32,600 15-Mar-2007 10:22 x86
System.web.dll 2.0.50727.819 5,156,864 15-Mar-2007 10:23 x86
Webengine.dll 2.0.50727.819 406,016 15-Mar-2007 10:22 x86


WORKAROUND

To work around this problem, delete all files in the Temporary ASP.NET Files directory. To do this, follow these steps:

  1. Click Start, click Run, type iisreset /stop, and then click OK.
  2. Open the DriveLetter: WINDOWS\Microsoft.NET\Framework\v2.0.50727\Temporary ASP.NET Files directory.
  3. Delete all files and all folders in the directory that you located in step 2.
  4. Click Start, click Run, type iisreset /start, and then click OK.

You can also work around this problem by setting the batch property of the compilation tag to false. To do this, follow these steps:

  1. In the Microsoft Visual Studio 2005 project, right-click Web.config in Solution Explorer, and then click Open.
  2. Locate the code that resembles the following.

    <compilation debug="false" />
  3. Replace the code that you located in step 2 with the following code.

    <compilation debug="false" batch="false" />

Note If you set the value of the numRecompilesBeforeAppRestart property in the compilation tag to a high number, such as 50, you will reduce the number of times that this problem occurs. The compilation tag will resemble the following after you set the numRecompilesBeforeAppRestart property.

<compilation debug="false" numRecompilesBeforeAppRestart="50" />

STATUS

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

MORE INFORMATION

For more information, 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


Keywords: kbbug kbfix kbqfe kbpubtypekc kbhotfixserver KB934839