FIX: "The XML File \\MyComputer\MyShare\Web.config Could Not Be Loaded" Error Message

This article was previously published under Q328534
This article has been archived. It is offered "as is" and will no longer be updated.
If your Web content is located on a share, and you are using Session State in your application, you may receive the following error message in the browser when you view pages in your application:
Server Error in '/MyApp' Application.

Configuration Error

Description: An error occurred during the processing of a configuration file required to service this request. Please review the specific error details below and modify your configuration file appropriately.

Parser Error Message: The XML file \\MyComputer\MyShare\web.config could not be loaded. Logon failure: unknown user name or bad password.

Source Error:
[No relevant source lines]					
Source File: \\MyComputer\MyShare\web.config
Line: 0

Version Information: Microsoft .NET Framework Version: 1.0.3705.288; ASP.NET Version: 1.0.3705.288
The following stack trace appears at the bottom of the HTML source page:
[ConfigurationException]: The XML file \\MyCopmuter\MyShare\web.config could not be loaded. Logon failure: unknown user name or bad password.
at System.Web.Configuration.HttpConfigurationRecord.Evaluate(String configKey, SectionRecord section)
at System.Web.Configuration.HttpConfigurationRecord.GetConfig(String configKey, Boolean cacheResult)
at System.Web.Configuration.HttpConfigurationRecord.get_Item(String configKey)
at System.Web.HttpContext.GetAppConfig(String name)
at System.Web.SessionState.SessionStateModule.Init(HttpApplication app)
at System.Web.HttpApplication.InitModules()
at System.Web.HttpApplication.InitInternal(HttpContext context, HttpApplicationState state, MethodInfo[] handlers)
at System.Web.HttpApplicationFactory.GetNormalApplicationInstance(HttpContext context)
at System.Web.HttpApplicationFactory.GetApplicationInstance(HttpContext context)
at System.Web.HttpRuntime.ProcessRequestInternal(HttpWorkerRequest wr)
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 fix. For a complete list of Microsoft Product Support Services phone 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 typical 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 at the beginning of this article.

Article ID: 328534 - Last Review: 12/07/2015 12:27:23 - Revision: 3.5

Microsoft .NET Framework 1.0, Microsoft .NET Framework 1.0 Service Pack 1, Microsoft .NET Framework 1.0 Service Pack 2

  • kbnosurvey kbarchive kbbug kbfix kbqfe kbnetframe100presp3fix kbhotfixserver KB328534