Good morning,

I recently setup dotnetnuke 4.9.0 for a client in a virtual directory of their site.  I believe they eventually tried to somehow copy instance to the root of their website in IIS.  The problem is after the application was removed manually the web.config settings seem to be cached somewhere in IIS.  Has anyone ever encountered this problem?  I restarted IIS and receycled the application pool the dotnetnuke instance is in but the site is still caching.  Here is the content of the client's web.config file:

<?xml version="1.0" encoding="utf-8"?>
<configuration>
        <system.web>
        <customErrors mode="Off" />
    </system.web>
</configuration>

Here is the error received when attempting to access any .aspx file:

Server Error in '/' Application.

---

Configuration Error

Could not load file or assembly 'DNNContentBuilder, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null' or one of its dependencies. Failed to grant minimum permission requests. (Exception from HRESULT: 0x80131417)
Source File: web.config    Line: 66

Clearly there's no line 66 in web.config.  The platform's using IIS 6.

Thanks,

jberganz

I assume, they used to use a module, which is now missing. Please describe, how the web sites are nested.

It turns out that wiping the root of the website of all DNN content cleared the cache after an IIS reset.  I imagine the code attempted to recompile and cleared the cache?  I hope this helps anyone with the same issue.