Asp Net Runtime Error Child Nodes Not Allowed
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the company Business Learn more about hiring developers or posting ads with us Stack Overflow Questions Jobs Documentation Tags Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow is a community of 4.7 million programmers, just like you, helping each other. Join them; it only takes a minute: Sign up Visual Studio Asp.net Website Compilation error: Child nodes not allowed up vote 1 down vote favorite 1 "Child nodes not allowed" seems to be notorious compilation error on Asp.net website if you do some googling. Environment: WinXp, VS2008 and VS2008 SP1, .NET 3.5 SP1 Behavior: create a brand new Asp.net website (not web application), then just build it, you got compilation error "Child nodes not allowed" on the Web.config on line where it says providerOption name="CompilerVersion" value="v3.5"/> I got this problem after I re-installed vs2008. Now, a lot of people are suggesting fixes but none worked for us. Only one guy mentioned he successfully got rid of this problem by re-installing windows, but we don't want to go that far if we don't have to. There is another person who opened a ticket to MS but hasn't gotten back a response yet. If there is anyone out there who has similar environment like us and know how to get around this problem, we'd really appreciate it!!! Edit The weirdest part of all this is that I don't know how I got it. It is a brand new box and brand new installation. asp.net visual-studio-2008 share|improve this question edited Feb 18 at 15:46 Daniel Mann 20.1k33363 asked Apr 2 '09 at 17:01 fanray 4,3441665102 add a comment| 3 Answers 3 active oldest votes up vote 2 down vote accepted My colleague just found a fix for this dreadful problem, it is a .NET Framework Cleanup Utility at http://cid-27e6a35d1a492af7.skydrive.live.com/self.aspx/Blog|_Tools/dotnetfx20|_cleanup|_tool.zip Just download, run and restart your machine and re-install .NET Framework 3.5 SP1 (since the cleanup util removes all the .NET Frameworks for you)! Really hope this could help others who have the same problem, it's been 4 days fighting with this one issue, thanks Microsoft! Thank you guys very much for your input, I voted up for you both, appreciate it! Ray. share|improve this answer answered Apr 2 '09 at 18:20 fanray 4,3441665102 @ray flag your own answer as the accepted answer :) –eglasius Apr 2 '09 at 18
you need to follow the steps below: Step 1: Download (Asp Net Runtime Error Child Nodes Not Allowed) Repair Tool Step 2: Click the "Scan" button Step 3: Click 'Fix All' and you're done! Compatibility: Windows 7, 8, Vista, XP Download Size: 6MB Requirements: 300 MHz Processor, 256 MB Ram, 22 MB HDD Limitations: This download is a free evaluation version. To unlock all features and tools, a purchase is required. Asp Net Runtime Error Child Nodes Not Allowed Error Codes are caused in one way or another by misconfigured system files in your windows operating system. If you have http://stackoverflow.com/questions/710651/visual-studio-asp-net-website-compilation-error-child-nodes-not-allowed Asp Net Runtime Error Child Nodes Not Allowed errors then we strongly recommend that you Download (Asp Net Runtime Error Child Nodes Not Allowed) Repair Tool. This article contains information that shows you how to fix Asp Net Runtime Error Child Nodes Not Allowed both (manually) and (automatically) , In addition, this article will help you troubleshoot some common error messages related to Asp Net Runtime Error Child Nodes Not Allowed error code that http://asp.net.runtime.error.child.nodes.not.allowed.cl-xml.org/ you may receive. Note: This article was updated on 2016-09-25 and previously published under WIKI_Q210794 Contents 1.What is Asp Net Runtime Error Child Nodes Not Allowed error? 2.What causes Asp Net Runtime Error Child Nodes Not Allowed error? 3.How to easily fix Asp Net Runtime Error Child Nodes Not Allowed errors What is Asp Net Runtime Error Child Nodes Not Allowed error? The Asp Net Runtime Error Child Nodes Not Allowed error is the Hexadecimal format of the error caused. This is common error code format used by windows and other windows compatible software and driver vendors. This code is used by the vendor to identify the error caused. This Asp Net Runtime Error Child Nodes Not Allowed error code has a numeric error number and a technical description. In some cases the error may have more parameters in Asp Net Runtime Error Child Nodes Not Allowed format .This additional hexadecimal code are the address of the memory locations where the instruction(s) was loaded at the time of the error. What causes Asp Net Runtime Error Child Nodes Not Allowed error? The Asp Net Runtime Error Child Nodes Not Allowed error may be caused by windows system files damage. The corrupted system files entries can be a real threat to the well being of your computer. There can be
MPP, images formats and many more! ASP.NET 1.1 working with an ASP.NET 2.0 web.config file Posted by Peter van Ooijen on June 23, 2006 In a recent post I described the http://codebetter.com/petervanooijen/2006/06/23/asp-net-1-1-working-with-an-asp-net-2-0-web-config-file/ trouble an asp.net 1.1 application has with a web.config file targeted at asp.net 2.0. The main problem is that the asp.net 1.1. runtime does not understand parts of the 2.0 web.config and crashes. My first solution was to move settings to the global 2.0 config. In a brilliant comment Joshua Flanagan suggested to bring the problem to its owner. His idea was to teach asp.net 1.1 the 2.0 asp net specific sections and tell it to ignore them. This sounds more complicated than it is and works well. For a good overview of the web.config in 1.x I again recommend James Avery little book, I blogged before on that. The global configuration of asp.net 1.x is in the machine.config file in \WINDOWS\Microsoft.NET\Framework\v1.x\CONFIG. (Note that 1.x does not have a global web.config like 2.0). This file has a list asp net runtime of sections and the assemblies to handle the sections. The framework has a very handy handler, the IgnoreSectionHandler. Which does exactly what's desired: nothing. This snippet tells asp.net to ignore the connectionstrings section