We are excited to announce that the IIS.NET Forums are moving to the new Microsoft Q&A experience. Learn more >

Does Not! [Answered]RSS

15 replies

Last post Nov 14, 2011 12:27 PM by xmas__

  • Does Not!

    May 06, 2008 07:59 PM|CleverHuman|LINK

    IIS 7 (Vista) is telling me this about my (VS2k8 automatically created) Virtual Directory:

    Detailed Error InformationModule IIS Web Core
    Notification BeginRequest
    Handler Not yet determined
    Error Code 0x800700b7
    Config Error There is a duplicate 'system.web.extensions/scripting/scriptResourceHandler' section defined 
    Config File \\?\c:\Dev\WebSites\LY\LYT\LY.Site\web.config
    Requested URL http://localhost:80/LY.Site/signup/newcompany.aspx
    Physical Path c:\Dev\WebSites\LY\LYT\LY.Site\signup\newcompany.aspx
    Logon Method Not yet determined
    Logon User Not yet determined

     

    It shows me this config source that it is objecting about:

        4: 			<sectionGroup name="scripting" type="System.Web.Configuration.ScriptingSectionGroup, System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35">
        5: 				<section name="scriptResourceHandler" type="System.Web.Configuration.ScriptingScriptResourceHandlerSection, System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35" requirePermission="false" allowDefinition="MachineToApplication"/>
        6: 				<sectionGroup name="webServices" type="System.Web.Configuration.ScriptingWebServicesSectionGroup, System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35">
    


    Unfortunately, it lies. Lies Lies Lies. There is no such duplicate section in my web.config. I hit CTRL+F and everything!

    Also, it appears no one else in the entire world of Google has had this specific problem. Not that it should matter... but this is a SilverLight2 beta app trying to communicate with a WCF webservice based web app. Though -- none of that should come into play when just parsing the web.config file.

    Any thoughts? There is no actual duplication here that I can see. Here is the full text of the configsecionts section of my web.config:

    <configSections>

    <sectionGroup
    name="system.web.extensions" type="System.Web.Configuration.SystemWebExtensionsSectionGroup, System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35">

    <sectionGroup name="scripting" type="System.Web.Configuration.ScriptingSectionGroup, System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35">

    <section name="scriptResourceHandler" type="System.Web.Configuration.ScriptingScriptResourceHandlerSection, System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35" requirePermission="false" allowDefinition="MachineToApplication"/>

    <sectionGroup name="webServices" type="System.Web.Configuration.ScriptingWebServicesSectionGroup, System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35">

    <section name="jsonSerialization" type="System.Web.Configuration.ScriptingJsonSerializationSection, System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35" requirePermission="false" allowDefinition="Everywhere"/>

    <section name="profileService" type="System.Web.Configuration.ScriptingProfileServiceSection, System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35" requirePermission="false" allowDefinition="MachineToApplication"/>

    <section name="authenticationService" type="System.Web.Configuration.ScriptingAuthenticationServiceSection, System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35" requirePermission="false" allowDefinition="MachineToApplication"/><section name="roleService" type="System.Web.Configuration.ScriptingRoleServiceSection, System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35" requirePermission="false" allowDefinition="MachineToApplication"/>

    </sectionGroup>

    </sectionGroup>

    </sectionGroup>

    </configSections>

     

  • Re: Does Not!

    May 06, 2008 11:03 PM|thomad|LINK

    You probably have a web.config file that has the same entry in a parent directory. Configuration inherits from the parent and that's generating the error.

     

    Hope this helps

    Thomas Deml
    Group Program Manager
    Internet Information Services
    Microsoft Corp.
  • Re: Does Not!

    Dec 09, 2008 06:59 PM|gponto18|LINK

    I just ran into this issue today on an application that was working; no code changed whatsoever. I cannot find any duplicate entry within my web.config file either.

    Anyone manage to overcome this one?

  • Re: Does Not!

    Feb 21, 2010 03:04 PM|DaGeneie|LINK

    I also ran into this issue today - but it was after I changed one of my sites from .Net 2.0 framework app pool to .Net 4.0 app pool.  As soon as I changed the app pool back to the Classic .Net app pool, the error went away. 

  • Re: Does Not!

    Mar 16, 2010 02:50 PM|Thomas.WCV|LINK

    That happened to me to. i updated to .NET 4.0 in hopes of resolving some AJAX errors and 'poof'! this error popped up. i'm going to switch back to 2.0 since it worked for you...thanks!

    -Thomas Shields - MPDT
  • Re: Does Not!

    May 16, 2010 11:46 PM|Hariom79|LINK

     Hi DaGeneie,

    I was also getting same problem and i used the method you suggested, i worked.

    Thanks

     

  • Re: Does Not!

    Jul 09, 2010 07:16 AM|fevriul|LINK

    The fix I found for this is to rebuild my Websiute using framework 4, and the problem went away, it seem if you mix and match frameworks on IIS 7 it can get its knickers in a twist.

  • Re: Does Not!

    Sep 30, 2010 01:32 PM|AlexGarcia|LINK

    The problem occurs because when you use framework 4.0 the machine config already has all those sections defined:

    So, you can remove them from your local web.config file safely.

    Please note that the versions used in the machine.config are 4.0.0.0. You should not have any problem with using the new versions at all.

    <sectionGroup name="system.web.extensions" type="System.Web.Configuration.SystemWebExtensionsSectionGroup, System.Web.Extensions, Version=4.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35">
       <sectionGroup name="scripting" type="System.Web.Configuration.ScriptingSectionGroup, System.Web.Extensions, Version=4.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35">
        <section name="scriptResourceHandler" type="System.Web.Configuration.ScriptingScriptResourceHandlerSection, System.Web.Extensions, Version=4.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" requirePermission="false" allowDefinition="MachineToApplication"/>
        <sectionGroup name="webServices" type="System.Web.Configuration.ScriptingWebServicesSectionGroup, System.Web.Extensions, Version=4.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35">
         <section name="jsonSerialization" type="System.Web.Configuration.ScriptingJsonSerializationSection, System.Web.Extensions, Version=4.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" requirePermission="false" allowDefinition="Everywhere"/>
         <section name="profileService" type="System.Web.Configuration.ScriptingProfileServiceSection, System.Web.Extensions, Version=4.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" requirePermission="false" allowDefinition="MachineToApplication"/>
         <section name="authenticationService" type="System.Web.Configuration.ScriptingAuthenticationServiceSection, System.Web.Extensions, Version=4.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" requirePermission="false" allowDefinition="MachineToApplication"/>
         <section name="roleService" type="System.Web.Configuration.ScriptingRoleServiceSection, System.Web.Extensions, Version=4.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" requirePermission="false" allowDefinition="MachineToApplication"/>
        </sectionGroup>
       </sectionGroup>
      </sectionGroup>

     

  • Re: Does Not!

    Jan 04, 2011 02:18 AM|nitin.virgo|LINK

    Thanks! It solved my problem after 3 sleepless nights.
  • Re: Does Not!

    Jan 04, 2011 04:29 AM|HCamper|LINK

    nitin.virgo

    Thanks! It solved my problem after 3 sleepless nights.

    Hello,

    Glad you got the problem fixed and maybe get some sleep.

    For your reply of "It solved my problem"

    leaves it open ended.

    The post here has a lot of steps.

    If you could reply with the exact steps you used.

    Please give more information to save the next reader a leg up on the resolutions.

    Martin :)

    Windows and Linux work Together IT-Pros
    Community Member Award 2011
  • Re: Does Not!

    Jan 05, 2011 11:55 PM|nitin.virgo|LINK

    I installed IIS 7.5 after installing .net 4.0. So when i was trying to run Aspnet_iisreg. It was giving error to run as administrator. So first step was before clicking on vs command prompt, right click on prompt and click on run as adminstrator, then run Aspnet_iisreg -i command. Now when i hosted my website on IIS, it was giving error of duplicate scriptResourceHandler. Which i solved with the steps told by "AlexGarcia". I removed "sectionGroup" portion from my webconfig, and it worked.
  • Re: Does Not!

    Jan 10, 2011 02:56 PM|bfc77usa|LINK

    Thanks for this info.  Removing the section from my web.config fixed the problem as it was duplicated in the machine.config. Had just moved to .NET Framework 4.0 app pools when the error started.

  • Re: Does Not!

    Apr 16, 2011 11:53 AM|eliassal|LINK

    I am really confused with what you said. I have a WWF hosted in IIS and getting the same error.

    In the web.config there is nothing except the following :

    <?xml version="1.0" encoding="utf-8" ?>

    <configuration>

    <system.web>

    <compilation debug="true" targetFramework="4.0" />

    </system.web>

    <system.serviceModel>

    <behaviors>

    <serviceBehaviors>

    <behavior>

    <!-- To avoid disclosing metadata information, set the value below to false and remove the metadata endpoint above before deployment -->

    <serviceMetadata httpGetEnabled="true"/>

    <!-- To receive exception details in faults for debugging purposes, set the value below to true. Set to false before deployment to avoid disclosing exception information -->

    <serviceDebug includeExceptionDetailInFaults="false"/>

    </behavior>

    </serviceBehaviors>

    </behaviors>

    </system.serviceModel>

    <system.webServer>

    <modules runAllManagedModulesForAllRequests="true"/> </system.webServer>

    </configuration>

     

    but still getting the same error when I try to browse. Can somebody tell me where is the duplication

    Thanks

  • Re: Does Not!

    Apr 16, 2011 12:19 PM|HCamper|LINK

    Hello @  eliassal ,

    As you may have noticed this is an old thread and is not getting updated replies.

    To get help and resolve issues create a new post with issue,errors information about your system. 

    Could you create a new post in the

    Web Deploy Forum http://forums.iis.net/1144.aspx or

    Web Farm Forum http://forums.iis.net/1167.aspx .

    When you create the new Post use as Question "I have a WWF hosted in IIS".

    The users / members in the specfic Forums then can help with answers / suggestions for you problem.

     Thank you for understanding,

    Martin

     

     

    Windows and Linux work Together IT-Pros
    Community Member Award 2011
  • Re: Does Not!

    Oct 25, 2011 09:47 PM|Tophers80|LINK

     The parent website is probably using .NET 2.0 and it's web.config is specifying extensions already in the machine.config for .NET 4.0. Now since all child applications inherit the parent website web.config, the extensions are referenced twice.

     Remove all the duplicate extensions from the parent web.config and move them to the root web.config for the 2.0 framework.

     

     

  • Re: Does Not!

    Nov 14, 2011 12:27 PM|xmas__|LINK

    Thank you! The same thing happened to me but it was a confing script that did the app pool change and I had no idea about it. Your post was very helpful!!!