.NET sites have a web.config file that configures all the settings. By default, most .NET sites will not include the setting to tell the children virtual directories to NOT inherit their parents settings. They also automatically inherit modules which sometimes will not load in the virtual directory.
Here are the steps to fix the issue with settings being inherited from the parent. Add or adjust the location tags above and below the system.web tags.
<location path=”.” inheritInChildApplications=”false”>
Another change you might need to make if the error loading is related to an http module, is to adjust the <httpmodules> section of the web.config of the actual EIOBoard virtual directory and add the <clear/> command.
The error will usually be something like this:
Parser Error Message: Could not load file or assembly ‘UrlRewritingNet.UrlRewriter’ or one of its dependencies. The system cannot find the file specified. (d:\Projects\VS\AspDotNetFaqProject\Website\web.config line 89)
The fix is to add the clear command in the httpmodules section:
This specifically discusses both of the potentially required changes discussed above:
In addition to these, you may need to adjust the http modules used in the VD and explicitly remove the modules erroring when the VD is launched or are known to not be inherited. Open IIS manager, drill down to the site, then drill down to the VD. On the right, you’ll see Modules on the right. Double click to launch it.
Sort by Code (click on the header). Look for the ones that are not native but are not syste
Select all of the ones you need to remove and click on remove on the right. Try the site out again and it should load as expected. You may need to do the same changes to the webservice and mobile folders if the interfaces won’t connect or the mobile won’t load.