Answered by:
Does Not!

Question
-
User1925722649 posted
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 determinedIt 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>
Tuesday, May 6, 2008 7:59 PM
Answers
-
User1356161706 posted
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
- Marked as answer by Anonymous Tuesday, September 28, 2021 12:00 AM
Tuesday, May 6, 2008 11:03 PM
All replies
-
User1356161706 posted
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
- Marked as answer by Anonymous Tuesday, September 28, 2021 12:00 AM
Tuesday, May 6, 2008 11:03 PM -
User-311224817 posted
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?
Tuesday, December 9, 2008 6:59 PM -
User1522919459 posted
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.
Sunday, February 21, 2010 3:04 PM -
User-779298769 posted
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!
Tuesday, March 16, 2010 2:50 PM -
User-33078322 posted
Hi DaGeneie,
I was also getting same problem and i used the method you suggested, i worked.
Thanks
Sunday, May 16, 2010 11:46 PM -
User-1357880678 posted
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.
Friday, July 9, 2010 7:16 AM -
User-759765249 posted
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>Thursday, September 30, 2010 1:32 PM -
User-1270067139 posted
Thanks! It solved my problem after 3 sleepless nights.Tuesday, January 4, 2011 2:18 AM -
User-1672167363 posted
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 :)
Tuesday, January 4, 2011 4:29 AM -
User-1270067139 posted
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.Wednesday, January 5, 2011 11:55 PM -
User-672322408 posted
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.
Monday, January 10, 2011 2:56 PM -
User-588325081 posted
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
Saturday, April 16, 2011 11:53 AM -
User-1672167363 posted
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
Saturday, April 16, 2011 12:19 PM -
User-546048753 posted
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.
Tuesday, October 25, 2011 9:47 PM -
User-1938893238 posted
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!!!Monday, November 14, 2011 12:27 PM