Take the 2-minute tour ×
Server Fault is a question and answer site for professional system and network administrators. It's 100% free, no registration required.

I have a Default Web site set up in IIS 7.5 on Win2008 Server R2.

There are multiple ASP.NET 2.0 applications under the Default Web site. Currently, I am trying to deploy a new precompiled ASP.Net 4.0 application to the Default Web site, but the Web server is returning a HTTP 500.19 error describing a duplicate 'system.web.extensions/scripting/scriptResourceHandler' section defined in the Web.config. However, the Web.config file path that the error references is for a different application under the Default Web site than the one I am trying to open.
For example, I am putting in the URL for the new ASP.NET 4.0 application but the Web.config error it is giving me is for one of the 2.0 applications. The virtual paths are correct and each application has its own App Pool.

Any ideas what may be causing this problem?

share|improve this question
    
Take a look at this, same kind of problem: stackoverflow.com/a/6200408/419 –  Kev Jul 18 '12 at 3:16
add comment

1 Answer

The root of your Default Web Site is an application too - you'll probably find it's using the DefaultAppPool and it's configured to use .Net 2.0. The configuration may be inherited from here.

You could try one of these:

  1. If there is no application configured at the root of the site you could try changing the DefaultAppPool settings to 'No Managed Code'
  2. Turn off inheritance from the root app using inheritInChildApplications="false"
  3. Use a <remove... > tag for each conflicting module before they get added with <add...>

Bear in mind that 1 and 2 could affect your child apps if they rely on any of the inherited settings.

share|improve this answer
    
I tried setting inheritInChildApplications="false" in my root web.config and all of my child Web sites went down. Every child app has its own Web.config, how can I make them ignore the root Web.config and just use there own? –  tony95 Jul 17 '12 at 14:40
    
As per the last line of my reply, your child web sites are probably relying on settings in the root web.config. Find out what they are and move the settings into your child web.configs –  Chris McKeown Jul 17 '12 at 14:53
add comment

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.