asked on

Child Nodes Not Allowed 3.5 Issue

I have a website that I have successfully deployed across a range of servers from XP 5.1 to IIS 7 servers. For some reason the same web.config file will not work on a Windows 2003 server running IIS 6. As you can see from the error below, the site is running under v2 and I tried uninstalling and reinstalling v3.5 (which is the codebase used to develop the site). This site literally works everywhere else so I know it is something outside of the web.config file. Does anybody have an idea on what the problem might be?

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 not allowed.
Source Error:

Line 137: <compilers>
Line 138: <compiler language="c#;cs;csharp" extension=".cs" warningLevel="4" type="Microsoft.CSharp.CSharpCodeProvider, System, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089">
Line 139: <providerOption name="CompilerVersion" value="v3.5"/>
Line 140: <providerOption name="WarnAsError" value="false"/>
Line 141: </compiler>

Source File: C:\Inetpub\wwwroot\FuserGifts\web.config Line: 139

Version Information: Microsoft .NET Framework Version:2.0.50727.42; ASP.NET Version:2.0.50727.210

prairiedog

It's a new tag in v3.5. ASP.NET 2.0 does not support it. See here:
http://forums.asp.net/t/1265071.aspx

ktola

ASKER

You are correct if you build a v2 website then this assembly binding tag will throw errors. However, it is absolutely necessary if you are using 3.5 as it is the only means for IIS to bind to the correct DLL.

To be clear, this site was built in VS 2008 targeting the .NET 3.5 Framework and that means that the tag in question is required. Further, this same exact site has worked on a range of servers but, for some reason, throws this error when I placed it on a 2003 Server running IIS 6.0. I have NO IDEA what the issue is...

Thanks!

prairiedog

Do you have Framework 3.5 installed on the 2003 server?

ktola

ASKER

I have the 3.5 framework on the server - and I actually went through, uninstalled and reinstalled it on my own just to make sure there were no issues there. I then read something about 3.5 not supporting 64-bit servers so I downgraded to 32-bit and that still did not work.

I have recompiled and pushed out the site again - thinking that might be the issue. I have manually checked the web.config for structural issues...nothing is working....

ktola

ASKER

So I have discovered that this "server" is actually a 64-bit VPS and I think that this might be the culprit even though the hosting provider says otherwise. Has anybody experience issues with the 3.5 framework not running properly on a 64-bit server? Is there a 64-bit 3.5 framework I should be using? Finally, is there some setting I cannot find in Visual Studio 2008 that forces it to use 64-bit versions of the framework?

My development environment, by the way, is 32-bit...

Thanks!

ASKER CERTIFIED SOLUTION

ktola

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial