I started to get the error a week ago where I started to receive "The requested page cannot be accessed because the related configuration data for the page is invalid." errors. When I was running Vista & IIS 7, installing DNN was a snap. I am certain that the issue is centered around permissions but I cannot find it. Here is what I have done so far. 1. Fresh Installation of Windows 7 Ultimate 32 bit. 2. I have two directories for web applications (c:\webapplications and c:\webDNNapplications). The security on the directories is set to allow NetworkServices Full Control. 3. In IIS, C:\webapplications is set for the location for the web site. I added Dev as a web application and pointed it to c:\webDNNApplications\LocalDNN512. 4. I changed the permissions on the ApplicationPools to be NetworkService vice default ApplicationPoolIdentity. 5. I downloaded a copy of DNN 5.1.2 Install file and moved contents to c:\webDNNApplications\LocalDNN512 6. When I attempt to load DNN (http://localhost/dev) I receive the following error information. HTTP Error 500.19 - Internal Server Error The requested page cannot be accessed because the related configuration data for the page is invalid. Detailed Error Information Module IIS Web Core Notification BeginRequest Handler Not yet determined Error Code 0x800700b7 - Config Error Cannot add duplicate collection entry of type 'add' with unique key attribute 'name' set to 'ScriptModule' - Config File \\?\C:\WebDNNApplications\LocalDNN512\web.config - Requested URL http://192.168.11.110:80/dev Physical Path C:\WebDNNApplications\LocalDNN512 Logon Method Not yet determined - Logon User Not yet determined Config Source 58: 59: 60: I have tried a number of changes with no impact. I would really appreciate any insight and something to correct this error if possible. I have some tasks that I need to get completed and this is holding me back. Thanks in advance Ray

Actually, I think that I figured it out and the solution was to change permissions to use the IIS AppPool\DefaultAppPool and a small change to web.config. In a nutshell; 1. Changed Application Pool back to ApplicationPoolIdentity 2. Added IIS AppPool\DefaultAppPool to the directory and Web Site permissions. Read http://learn.iis.net/page.aspx/624/...dentities/ for directions to change directory permissions. To change the web server permissions, -> in the IIS Manager, click on the main Web Site -> in the right column, click on Edit Permissions. -> Use the same process for changing the permissions as you did for the directory 3. Added the following line to the web.config under 4. At this point if you attempt to install DNN, you might get an error message regarding incorrect casting of the ScriptModule. This issue is caused when the root web has references to .NET Framework 3.5 as when a website exists at http://localhost that uses Framework 3.5. I removed the files from my root web and DNN installed normally. Based on what I read, IIS 7.5 is configured to use IIS AppPool\DefaultAppPool which offers additional security instead of using NetworkService. The referenced article makes note of the setting. There are a number of articles that explain how this permission set functions. Regarding removing the root web.config file if it referenced .NET Framework 3.5, I found a this reference on the DotNetNuke Forums. I was able to complete an installation of DNN and it is up and running. Now I can rest comfortably. Thanks Ray

Great!

Hi,
I have the same problem. Could you tell me what did you add in the web.config file ?
Thanks

The main issues was that you have to given the directories permissions to AppPool\DefaultAppPool. Secondly, the root of the problem is when there is a web site at the root of the web server.

My web server configuration had a web installation and web.config file at its root (http://localhost/). When I deleted the root wen.config file at the root, the problem went away.

Hope that helps
Ray