child nodes not allowed

Hey guys I am getting an error with the website I have recently launched.
When I load my web page it runs this error

Server Error in '/' 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: Child nodes are not allowed.

Source Error:


Line 25: <compilation debug="true"/>
Line 26: <pages>
Line 27: <namespaces>
Line 28: <clear/>
Line 29: <add namespace="System"/>


Source File: C:\WebSites\kidsinfrance\web.config Line: 27


--------------------------------------------------------------------------------
Version Information: Microsoft .NET Framework Version:1.1.4322.2407; ASP.NET Version:1.1.4322.2407

Does anyone have any idea what the problem is?

Thanks for anyhelp

What does your Web.config look like? We can see a few lines but that error states that it's not formatted correctly in Xml.

Here is my xml file

HTML Code:

---

<?xml version="1.0"?>
<!--
    Note: As an alternative to hand editing this file you can use the
    web admin tool to configure settings for your application. Use
    the Website->Asp.Net Configuration option in Visual Studio.
    A full list of settings and comments can be found in
    machine.config.comments usually located in
    \Windows\Microsoft.Net\Framework\v2.x\Config
-->
<configuration>
        <appSettings/>
       
        <system.web>
                <!--
            Set compilation debug="true" to insert debugging
            symbols into the compiled page. Because this
            affects performance, set this value to true only
            during development.

            Visual Basic options:
            Set strict="true" to disallow all data type conversions
            where data loss can occur.
            Set explicit="true" to force declaration of all variables.
        -->
                <compilation debug="true"/>
                <pages>
                        <namespaces>
                                <clear/>
                                <add namespace="System"/>
                                <add namespace="System.Collections"/>
                                <add namespace="System.Collections.Specialized"/>
                                <add namespace="System.Configuration"/>
                                <add namespace="System.Text"/>
                                <add namespace="System.Text.RegularExpressions"/>
                                <add namespace="System.Web"/>
                                <add namespace="System.Web.Caching"/>
                                <add namespace="System.Web.SessionState"/>
                                <add namespace="System.Web.Security"/>
                                <add namespace="System.Web.Profile"/>
                                <add namespace="System.Web.UI"/>
                                <add namespace="System.Web.UI.WebControls"/>
                                <add namespace="System.Web.UI.WebControls.WebParts"/>
                                <add namespace="System.Web.UI.HtmlControls"/>
                        </namespaces>
                </pages>
                <!--
            The <authentication> section enables configuration
            of the security authentication mode used by
            ASP.NET to identify an incoming user.
        -->
                <authentication mode="None"/>
                <!--
            The <customErrors> section enables configuration
            of what to do if/when an unhandled error occurs
            during the execution of a request. Specifically,
            it enables developers to configure html error pages
            to be displayed in place of a error stack trace.

        <customErrors mode="RemoteOnly" defaultRedirect="GenericErrorPage.htm">
            <error statusCode="403" redirect="NoAccess.htm" />
            <error statusCode="404" redirect="FileNotFound.htm" />
        </customErrors>
        -->

  <customErrors mode="Off"/>
     
       
  </system.web>
</configuration>

---

According to the MSDN, the Namespaces in your Web.config should be declared at the root of the Web.config. Perhaps that is the issue? I am unfamiliar with declaring namespaces in the Web.config.

Check this also, googling it made it look like a common problem is your .Net version.

Make sure you have .Net 2.0 or higher installed and check what version your virtual directory is running under.

Parser Error: Child nodes are not allowed


http://www.ironspeed.com/Designer/3....ot_allowed.htm

So it has nothing to do with the server I am running under. Cause the person who hosts my website had an older version of .net and he is installing the new one.

Quote:

---

Originally Posted by tarik666

So it has nothing to do with the server I am running under. Cause the person who hosts my website had an older version of .net and he is installing the new one.

---

No it does have something to do with the server it's being hosted on. According to Metallicaman's post, you need to have ASP.Net 2.0 or higher and since your host said they have the older one, then it wouldn't work.

Next time please post the version of .Net you're using as well as the host you're deploying to; it makes our jobs easier.

Your error message indicates

Quote:

---

Version Information: Microsoft .NET Framework Version:1.1.4322.2407; ASP.NET Version:1.1.4322.2407

---

If they say they have 2.0, then you will need to either via them or via your control panel configure your site to use 2.0 rather than 1.1

well I think my virtual directory is configured for .net 2.0 and the server dude is downloading 3.5 and I have 3.5 but I cant set the virtual directory to 3.5

Technically speaking, there is no ASP.NET 3.5. It's just ASP.NET 2.0 using the .NET 3.5 framework.

If you're still getting the same error and the version information at the bottom shows 1.1, then your virtual directory is not configured for .NET 2.0. You will need to confirm this, be 100% sure.

Alright. The man that runs my server is checking his directory for my site. Checking that he is running a 2.0 version