Microsoft KB Archive/307506

= BUG: ASP.NET runtime rejects configuration file as invalid =

Article ID: 307506

Article Last Modified on 1/25/2006

-

APPLIES TO


 * Microsoft Windows Management Instrumentation in . NET
 * Microsoft .NET Framework 1.1
 * Microsoft .NET Framework 1.0
 * Microsoft Visual Studio .NET 2003 Professional Edition
 * Microsoft Visual Studio .NET 2002 Professional Edition

-



This article was previously published under Q307506



SYMPTOMS
If a configuration file does not already contain a  Extensible Markup Language (XML) element, and the first instance of a configSection class is written to the configuration file by using the configuration Windows Management Instrumentation (WMI) provider, the  XML element may be written after other XML elements (and therefore appear later in the configuration file). This causes the ASP.NET runtime and other parts of the .NET Framework to reject the configuration file as invalid.



CAUSE
This behavior occurs because the configuration WMI provider does not provide control over the ordering of XML elements in configuration files. It merely preserves the existing order in the configuration file.



RESOLUTION
To work around this issue, start with an empty configuration file (or a nonexistent configuration) and make sure that the first instance being written to the file is an instance of the configSection WMI class.

You can also write an empty  XML element to the file through other means (for example, manually use a text editor, through an XML parser, to directly access the file).



STATUS
Microsoft has confirmed that this is a bug in the Microsoft products that are listed in the &quot;Applies to&quot; section.

Additional query words: kbreadme

Keywords: kbtshoot kbbug kbnofix kbreadme kbvs2002sp1sweep kbvs2005swept kbvs2005doesnotapply KB307506

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.