I am trying to set up a local copy of my site on a new Win 7 machine that uses IIS 7.5.  I've done it previously on an XP system but am new to Windows 7.  I have added a local web site and placed all backup files in the virtual directory but get the following error(s) when attempting to browse to http://localhost/<sitename>.  Are there any guidelines available.  Thanks.

Configuration Error

Description: An error occurred during the processing of a configuration file required to service this request. Please review the specific error details below and modify your configuration file appropriately.

Parser Error Message: It is an error to use a section registered as allowDefinition='MachineToApplication' beyond application level.  This error can be caused by a virtual directory not being configured as an application in IIS.

Source Error:

Line 99:   </system.webServer> Line 100:  <system.web> Line 101:    <machineKey validationKey="3202FDE99F0F376F3911DE862D69215BA25E2495" decryptionKey="C1C00BE77C0B0A3B71374F809FC3E8E151D6FDB8A2693A89" decryption="3DES" validation="SHA1" /> Line 102:    <!-- HttpModules for Common Functionality --> Line 103:    <httpModules>

Source File: C:\inetpub\wwwroot\biusa_win7\web.config    Line: 101
Show Additional Configuration Errors:

It is an error to use a section registered as allowDefinition='MachineToApplication' beyond application level.  This error can be caused by a virtual directory not being configured as an application in IIS. (C:\inetpub\wwwroot\biusa_win7\web.config line 166) It is an error to use a section registered as allowDefinition='MachineToApplication' beyond application level.  This error can be caused by a virtual directory not being configured as an application in IIS. (C:\inetpub\wwwroot\biusa_win7\web.config line 226)
 
 

It is an error to use a section registered as allowDefinition='MachineToApplication' beyond application level.  This error can be caused by a virtual directory not being configured as an application in IIS. (C:\inetpub\wwwroot\biusa_win7\web.config line 227)

 

Version Information: Microsoft .NET Framework Version:4.0.30319; ASP.NET Version:4.0.30319.272

 

When setting up the site in IIS Manager you must use "Add Application", not "Add Virtual Directory".

Also, since you indicated that you are using IIS 7.5, I'll direct you to an excellent article on IIS.Net which explains which account needs to be granted full file system permissions (including modify) on the root folder of the site and all child folders:

http://learn.iis.net/page.aspx/624/ap...

This is one of the major differences with IIS 5.1 (XP), etc. and a frequent sources of problems when setting up DotNetNuke on IIS 7.5.

---

Bill, WESNet Designs
Team Lead - DotNetNuke Gallery Module Project (Not Actively Being Developed)
Extensions Forge Projects . . .
Current: UserExport, ContentDeJour, ePrayer, DNN NewsTicker, By Invitation
Coming Soon: FRBO-For Rent By Owner

I found a video tutorial on dnncreative.com that explains installation under iis 7.5 on Win 7 Pro. It also mentions using Add Application as Bill (above) mentioned. I found the folloeing problem:

When I added Application under IIS I did not see/have the option to select Classic .NET App Pool. Not sure why>

After following instructions I now get the following error when I try to access my restored site. Anyone have any help or suggestions?

Thanks. Al

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 0x80070021
Config 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".
Config File \\?\C:\DNN_Sites\BIUSABkUp\web.config
Requested URL http://localhost:80/biusabkup
Physical Path C:\DNN_Sites\BIUSABkUp
Logon Method Not yet determined
Logon User Not yet determined
Config Source
80:
81:
82:
Links and More Information This error occurs when there is a problem reading the configuration file for the Web server or Web application. In some cases, the event logs may contain more information about what caused this error.