# Config Error: This configuration section cannot be used at this path if we run VC3 in IIS

**URL:** <https://www.virtocommerce.org/t/config-error-this-configuration-section-cannot-be-used-at-this-path-if-we-run-vc3-in-iis/206>\
**Category:** dev\
**Tags:** platform-v3, iis, configuration\
**Created:** [April 15, 2020, 7:14am UTC](https://www.virtocommerce.org/t/config-error-this-configuration-section-cannot-be-used-at-this-path-if-we-run-vc3-in-iis/206 "2020-04-15T07:14:29Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![OlegoO](https://yyz2.discourse-cdn.com/flex032/user_avatar/www.virtocommerce.org/olegoo/32/27_2.png) [@OlegoO](https://www.virtocommerce.org/u/OlegoO)\
**Post date:** [April 15, 2020, 7:14am UTC](https://www.virtocommerce.org/t/config-error-this-configuration-section-cannot-be-used-at-this-path-if-we-run-vc3-in-iis/206/1 "2020-04-15T07:14:29Z")

</div>

If you are trying to load the home page, or access authentication on the new site in IIS and get the error:

_This configuration section cannot be used at this path. This happens when the section is locked at a parent level. Locking is either by default (overrideModeDefault=“Deny”), or set explicitly by a location tag with overrideMode=“Deny” or the legacy allowOverride=“false”._

**To fix it:**  
Browse to “C:\Windows\System32\inetsrv\config” (you will need administrator rights here) Open applicationHost.config

**Note** : In IISExpress and Visual Studio 2015 the applicationHost.config is stored in `$(solutionDir).vs\config\applicationhost.config`

Find the section that showed up in the “config source” part of the error message page. Typically “modules”.

Change the `overrideModeDefault` attribute to be `Allow`.

So the whole line now looks like:

```auto
<section name="modules" allowDefinition="MachineToApplication" overrideModeDefault="Allow" />

```

After saving the file, the page should be loaded up fine in the browser.