cmerlo1
asked on
ASP.net Web.Config Parser Error Message: Child Nodes Not Allowed
I'm getting the following error whenever I try to access my pages:
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: Child nodes not allowed.
Source Error:
Line 14: <compilers>
Line 15: <compiler language="c#;cs;csharp" extension=".cs" type="Microsoft.CSharp.CSh
Line 16: <providerOption name="CompilerVersion" value="v3.5"/></compiler>
Line 17: <compiler language="vb;vbs;visualbas
Line 18: <providerOption name="CompilerVersion" value="v3.5"/></compiler><
Source File: \\shared.hosting.local\nfs
--------------------------
Version Information: Microsoft .NET Framework Version:2.0.50727.832; ASP.NET Version:2.0.50727.832
How do I fix this? My site is currently down...
--Christian
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: Child nodes not allowed.
Source Error:
Line 14: <compilers>
Line 15: <compiler language="c#;cs;csharp" extension=".cs" type="Microsoft.CSharp.CSh
Line 16: <providerOption name="CompilerVersion" value="v3.5"/></compiler>
Line 17: <compiler language="vb;vbs;visualbas
Line 18: <providerOption name="CompilerVersion" value="v3.5"/></compiler><
Source File: \\shared.hosting.local\nfs
--------------------------
Version Information: Microsoft .NET Framework Version:2.0.50727.832; ASP.NET Version:2.0.50727.832
How do I fix this? My site is currently down...
--Christian
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Christopher Kile
Sorry, when I wrote "line" I meant "element".
ANOTHER SOLUTION:
1) Make a copy of your webconfig.
2) Delete the webconfig from your project.
3) Reset your connection strings for your SQL datasources
4) Run debugger and recuild your webconfig.
I had this problem with Visual Web Developer 2008 projects created at work that don't play nicely with Visual Web Developer 2005 installed on my machine at home. This solves my problem every time.
1) Make a copy of your webconfig.
2) Delete the webconfig from your project.
3) Reset your connection strings for your SQL datasources
4) Run debugger and recuild your webconfig.
I had this problem with Visual Web Developer 2008 projects created at work that don't play nicely with Visual Web Developer 2005 installed on my machine at home. This solves my problem every time.
jazief,
I'll remember your technique for clearing web.configs that are incompatible going from VS2008 to VS2005...but the problem statement doesn't even mention SQL datasource access. This was a very specific problem that was solved by one step:
1. Delete the two illegal <providerOption> elements.
Why use four steps when one will do?
I'll remember your technique for clearing web.configs that are incompatible going from VS2008 to VS2005...but the problem statement doesn't even mention SQL datasource access. This was a very specific problem that was solved by one step:
1. Delete the two illegal <providerOption> elements.
Why use four steps when one will do?
RE: "Why use four steps when one will do?"
Your simple two-step solution doesn't work for me---I tested it.....but my solution works for me. I mentioned SQL datasources because deleting a webconfig also deletes any connection strings that may be included in the webconfig-----you knew this right?
Why assume your solution is the only answer to the problem. Different issues can in fact return the same types of error messages, thus requiring different types of solutions.
I was trying to be helpful to passers-by who may not have success with your situation-specific one-dimensional solution to this error message.
Your simple two-step solution doesn't work for me---I tested it.....but my solution works for me. I mentioned SQL datasources because deleting a webconfig also deletes any connection strings that may be included in the webconfig-----you knew this right?
Why assume your solution is the only answer to the problem. Different issues can in fact return the same types of error messages, thus requiring different types of solutions.
I was trying to be helpful to passers-by who may not have success with your situation-specific one-dimensional solution to this error message.
jazief,
I was trying to be kind. Your "solution" isn't a solution to THIS problem at all. It's completely irrelevant to the specific problem the original asker was asking.
I was trying to be kind. Your "solution" isn't a solution to THIS problem at all. It's completely irrelevant to the specific problem the original asker was asking.