Comments on: Configuring IIS 7 default document from web.config http://martinnormark.com/2007/12/20/configuring-iis-7-default-document-from-web-config?utm_source=rss&utm_medium=rss&utm_campaign=rss Wed, 10 Mar 2010 13:52:09 +0000 hourly 1 http://wordpress.org/?v=3.0.1 By: Martin H. Normark http://martinnormark.com/2007/12/20/configuring-iis-7-default-document-from-web-config/comment-page-1#comment-1010 Martin H. Normark Thu, 28 May 2009 10:28:49 +0000 /post/Configuring-IIS-7-default-document-from-webconfig.aspx#comment-1010 @Niskov This is because the settings has been locked through the applicationHost.config file located in C:\Windows\System32\inetsrv\config. As the error message points out, this is due to the allowOverride=false setting. Have a look in the applicationHost.config file and find the defaultDocument configuration element and look for the allowOverride property. @Niskov

This is because the settings has been locked through the applicationHost.config file located in C:\Windows\System32\inetsrv\config.

As the error message points out, this is due to the allowOverride=false setting. Have a look in the applicationHost.config file and find the defaultDocument configuration element and look for the allowOverride property.

]]> By: Niskov Fliskov http://martinnormark.com/2007/12/20/configuring-iis-7-default-document-from-web-config/comment-page-1#comment-1009 Niskov Fliskov Thu, 28 May 2009 09:16:45 +0000 /post/Configuring-IIS-7-default-document-from-webconfig.aspx#comment-1009 Thanks for the great article. I've tried what you said, but I always get the same "Configuration Error" (caused by "<system.webServer>"): "This configuration section cannot be used at this path. This happens when the site administrator has locked access to this section using <location allowOverride="false"> from an inherited configuration file." This is a real issue, since we use to deploy the site on many computers, and any configuration of the system will cause a tremendous overhead... any ideas? Thanks for the great article.
I’ve tried what you said, but I always get the same "Configuration Error" (caused by "<system.webServer>"):
"This configuration section cannot be used at this path. This happens when the site administrator has locked access to this section using <location allowOverride="false"> from an inherited configuration file."

This is a real issue, since we use to deploy the site on many computers, and any configuration of the system will cause a tremendous overhead… any ideas?

]]>