It's Windows 7 Ultimate and IIS 7.5. I don't see any part of the installation wizard, it happens immediately.
I had installed all important updates for the operating system before starting the various installations.

If I were you, I'd delete the website and try it again.  Pay special attention to everything.  Make sure that the IIS worker task assigned to the site in IIS is the same one that has permissions to the web directory.

Here is a comment from the DotNetNuke forums that sounds potentially applicable to your situation:

"

So the Application Pool in Windows7's IIS is running under the iden y called

ApplicationPoolIden y

This is apparently some sort of dynamic account that gets created based on the application pool. I changed the app pool for the website to run under the Network Service account (like Windows 2003/Vista/2008 default to) and then the install wizard fires up for DNN.

So this weekend I'll do some work on figuring out what ApplicationPoolIden y means in regards to DNN permissions."

-----------------

Actually, it was on Chris Hammond's blog: http://www.dotnetnuke.com/Community...ows-7.aspx

I changed the application pool default Iden y setting for Classic .Net AppPool to NetworkService, but I am still unable to install DNN. I am getting this error: DotNetNuke Configuration Error Could not find a part of the path 'C:\DotNetNukeSites\DNN_542\Config\Backup_2010612914\web_.config'.Access to the path 'C:\DotNetNukeSites\DNN_542\web.config' is denied. Your DotNetNuke installation appears to have a security settings problem (most likely permissions). DotNetNuke has extensive file upload capabilities for content, modules, and skins. These features require custom security settings so that the application is able to create and remove files in your website. Using Windows Explorer, browse to the root folder of the website ( C:\DotNetNuke by default ). Right-click the folder and select Sharing and Security from the popup menu ( please note that if you are using Windows XP you may need to Disable Simple File Sharing before these options are displayed ). Select the Security tab. Add the appropriate User Account and set the Permissions. Your Operation System appears to be Windows Server 2008 If using Windows 2000 - IIS5 ◦the [SERVER]\ASPNET User Account must have Read, Write, and Change Control of the virtual root of your website. If using Windows 2003 - IIS6 or Vista/Windows 2008 - IIS7 ◦the NT AUTHORITY\NETWORK SERVICE User Account must have Read, Write, and Change Control of the virtual root of your website. ************************************************* How do I know which account needs to be added to the my C:\ root folder? Right now I have listed in the Security tab for Group or User names: Users Administrators my name NETWORK SERVICE SYSTEM Authenticated Users CREATOR OWNER

I was able to combine the instructions from the blog link you provided and this site


http://blog.nddllc.com/2010/03/24/i...n-iis-7-5/


and I was able to complete the install for DNN. Thank you for your help.

Do you know what the problem was?

For the Classic .Net AppPool and DefaultAppPool I changed the Identi ty setting to NetworkService and the Load User Profile setting to true.

I found these settings by clicking on the Application Pools node under the computer name in the Connections panel in IIS Manager, clicking on the AppPool name, and then under Edit Application Pool I clicked on Advanced Settings.
(I'm sure you know where to find these, but it took me a while)

http://blogs.iis.net/webdeveloperti...bsp;y.aspx The default setting was changed from NetworkService to ApplicationPoolIden y

I recently upgraded my pc to windows 7 and followed this tutorial to set up a local copy of our production intranet for testing purposes (as I had on win xp). It loads fine on localhost, all the info is there except for images. If i right click and look at the properties/url they all show localhost/Portals/0/imagename. The site name/alias is missing. If I add a new image to something, it shows up fine and properties/url show as localhost/sitename/Portals/0/imagename I've checked every setting i can think of. Any suggestions what i need to change so the images show up? Thanks!

Unfortunately, you will need to manually edit all of the URLs to include the alias.

If most of the images are in HTML modules, you can use the free F3 module from EngageSoftware.com to do this.  If you move the resulting site back to production.  You will need to edit on that end, too.

The way to work around this issue is to install DotNetNuke locally as its own website and without an alias.  Right now, you have it installed as a subdirectory of the default website.

Thanks Joe.  I downloaded F3 and it took care of all but a few that I subsequently changed manually...

Just remember to keep good notes so it will be easier.

Installing DNN 5.06 on WIn7, SQL Exprs 2008.on options screen (Custom, Typical, Auto). The Auto option is disabled and text says "The Auto option has been disabled as the DotNetNuke Application cannot connect to a valid SQL Server database. Click Next It passes the permission checks. click next. Run as DB owner check box is disabled and "Test Database Connetion" button is missing. Click Next I get, Connection Error(s): Index #: 0 Source: .Net SqlClient Data Provider Class: 14 Number: 15372 Message: I would Appreciate your help to resolve this.

You'll need to specify the server, the database name and the username and password to use.  Generally, I'll first create an empty database using SQL Server Management Studio before starting the wizard.

When Installing there is a box for DB name. But where do I give user name and password. Is there a documenation on what kind of access the new user should have and what file and what code in the file I need to modify. What is it now and what should I modify it to be. Thansk

If you uncheck the box for integrated security, the wizard will display boxes for username and password.

You'd database user needs to have dbo privileges.

Hi, I followed the tutorial and was able to install the site ok and it works well. I'm building custom modules and I want to be able to debug the modules with Visual Web Developer 2010. I can start the site ok in debug mode, but if I try to set break points I get the message: "The breakpoint will not be hit. No symbols have been loaded for this document." I've got a clean install of vwd with the default settings. I've debugged DNN with vwd 2005 in the past. Is there something I need to configure? Thanks, all help is appreciated.

I'm trying to remember ... somewhat unsuccessfully ... what causes this.

Make sure that you are in Debug mode (though I'm certain that you are).  Also, set debug="true" in your web.config file.

I've mostly switched over to the so-called WAP method for developing and debugging modules.  Unfortunately, that requires Visual Studio, not the express version.  If you are going in that direction, be sure to see Chris Hammond's fairly recent series of blog entries on the DotNetNuke.com site.

For your case, you might want to look through the set of tutorials at adefwebserver.com.  I believe that these cover the case of using VS Express.  I think that also includes VWD Express.

I Googled a bit more and found this from Shawn Mehaffie, responding to a Michael Washington blog post.

Here is Shawn's contribution:



    Re: The Fastest Easiest Development Environment (without using IIS)

    I have been pulling my hair out because I could not get it to debug, unless I attached the process after the site has loaded. I search the internet, checked all the VS.Net setting, Solution and Project settings and it still did not work. I finally figured out the issue, see below:

    I have a VD under my web root called DNNFramework and then under that directory I have multiple DNN installations (DotNetNuke_Dev, DotNetNuke_Test, DotnetNuke_ModDev, etc). When I installed each of these DNN instances I used the IIS URL (ex: http:\DNNFramework\DotNetNuke_Dev) and it installed correctly. When I opened the web site using the file system and tried to debug the thing I did not notice was that it was opening up the site using the http:\DNNFramework\DotNetNuke_Dev URL instead of the http://localhost:8080/DotNetNuke_Dev is expected. It finally dawned on me that DNN was redirecting the site to the IIS URL because the other alias did not exist. I then added http://localhost/DotNetNuke_ModDev to the alias table and the debugging now works and this all makes sense now. The internal web server attached to the debugger, but it was never being hit because of the redirect. Adding the alias stopped the redirect and debugging works as expected.

    Lessons

    1) Alway pay attention to the URL in the browser when you are debugging / tracking down issues.
    2) Always remember DNN redirects to the first alias in the list if the one you used does not exist in the table.

    This is really only an issue for those who use IIS to install DNN before they open the site in VWD / VS. If you follow the directions Micheal sets out and access the site from within VWD / VS the first time the alias is added for you and you are good to go.

I have just completed the five video tutorials, using DNN 5.5.1. I must say the subscription was an excellent investment. Lee's step-by-step guide is indispensable for anyone venturing into this technology for the first time. I strongly recommend it.

Having made some instructional videos myself, I realize these videos are time-consuming to produce and require a lot of work. Also, technology is constantly changing, so it's hard to keep up. However, it would be nice if they were brought up to date. The SQL Server Express version recommended by Lee is no longer available from Microsoft. The videos still work, but if you are a complete newbie to SQL Server (like me), there are minor discrepancies that are confusing and worrisome.

I "hit the wall" when came time to install DNN. I got the dreaded "DNN can't connect to SQL" red error message. I spent a lot of time going over the previous steps, assuming it was my fault. I spent hours googling the error, learning more than I ever cared to about "Application Pool Ident-ities". When I finally forged ahead with Video #5, the problem sorted itself out. So I would suggest incorporating these steps prior to #4, installing DNN.

Still, for someone who has never installed IIS, SQL Server or DNN, I was very pleased to get my test site up & running. I will be avidly looking at all the other tutorials offered by DNNCreative.

I don't see the Classic .NET AppPool for selection in IIS 7.5. I have Visual Studio 2010, 2008 and 2005 installed on my Windows 7 installation. I have .NET Compact Framework 1.0 SP3 Developer, Compact Framework 2.0 SP2 , Compact Framework 3.5 as well as the .NET Framework 4 Client Profile and Extended.

I chose defaultappPool as I had no other choice, and I get the following error when I navigate to install DNN;

Http error 404.3 Not Found
The page you are requesting cannot be served because of the extension configuration. It the page is a script, add a handler. If the file should be downloaded, add a MIME map.

in the Detailed Error information the error code = 0x80070032

Thanks for your help.

Ed Schultheiss

I don't have a machine running IIS 7 handy.

You should be able to create a new AppPool and assign it to your DotNetNuke installation. Here are some instructions from a Microsoft help page:

To create an application pool on a Web server

You can perform this procedure by using the user interface (UI), by running Appcmd.exe commands in a command-line window, by editing configuration files directly, or by writing WMI scripts.

User Interface

To use the UI

1. Open IIS Manager. For information about opening IIS Manager, see Open IIS Manager (IIS 7).
2. In the Connections pane, expand the server node and click Application Pools.
3. On the Application Pools page, in the Actions pane, click Add Application Pool.
4. On the Add Application Pool dialog box, type a friendly name for the application pool in the Name box.
5. From the .NET Framework version list, select the version of the .NET Framework required by your managed applications, modules, and handlers. Or select No Managed Code if the applications that you run in this application pool do not require the .NET Framework.
6. From the Managed pipeline mode list, select one of the following options:
* Integrated, if you want to use the integrated IIS and ASP.NET request- processing pipeline.
* Classic, if you want to use IIS and ASP.NET request-processing modes separately. In classic mode, managed code is processed by using Aspnet_isapi.dll instead of the IIS 7 integrated pipeline.
7. Select Start application pool immediately to start the application pool whenever the WWW service is started. By default, this is selected.
8.
Click OK.

------------------
So, "Classic" is a parameter you can set for the AppPool.