Add any comments or questions regarding the How to install DotNetNuke to Windows 7 tutorial from Issue 51.

Lee,

This was helpful. I setup W7 in a virtual system like you suggested since I had trouble installing DNN after having used Visual Studio 2010 with ASP.net 4.0.

One suggestion is to highlight that SQL Express error in the 4th video. I ran into that and spent a good bit of time getting DNN to install - if I had just watched the 5th video I would have saved a lot of time...

thanks,
Dan

Hi Lee, I'm looking to upgrade to Windows 7 however I cannot use SQL Server 2008 Express with my current hoster. Do you know if Windows 7 runs with SQL Server 2005 Express (on Win 7 Home Premium) and DotNetNuke? Cheers, Celeste.

I haven't tested SQL 2005 on windows 7, but I would think it should be ok. - Just check the computer specs they provide in the install info. Thanks,

Lee, I signed up today and became a customer. Immediately my investment paid off because of your *thorough* videos. I can't wait to spend the next few months moving from beginner to advanced. I'm so excited.

May i ask you what may be a home networking question? I installed DNN on a desktop running W7 Ultimate and SQLServer 2008. I have several computers running on my home windows network, a Netgear Wireless router, all of them W7 Ultimate, and wish to run the DNN site i created on the computer i installed it on. While i can 'ping' that computer from all of my other computers, when i type the URL of the computer and the DNN site name (http://britbotpc-pc/dnn_522_tutoria...ult.aspx),
the browser on the other computers i'm working on jumps to localhost on that computer and doesn't even recognize my dotnetnuke site on the other computer.

Perhaps i'm missing something that would allow other computers on my home network, an intranet, to connect to the DNN site i set up?? Can you point me in a direction? Like i said, i can ping it OK,,,

Thanks again,

Robert

The fact that your site is redirecting to "localhost" is your indicator that the "portalalias" for the site is incorrect.  You will want to add a portal alias like this to your site:

              britbotpc-pc/dnn_522_tutorial

Thank you Joe!! Worked like a charm!! Now, i have a *ton* of videos to watch (i just signed up yesterday)! ..gotta go, popcorn's ready!

I am getting a 500.19 error when I try to run the DNN install. See Below. I have tried to change permissions on the site but that doesnt change anything with the error, Any ideas?


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:\Dotnetnuke sites\DNN_5_site\web.config

It is an IIS error.  This thread may be related.

That was it. All I had to do was delete the default website that IIS installed and it work fine. Thanks for the quick reply.

Lee I just installed Windows 7 Pro (64 bit) on a spare disk of my system and am trying to setup DNN 5.2.2. When I followed the IIS 7.5 setup from your video I didn't have the "Classic.Net AppPool" at first. It only appeared later after messing with SQL Server Express. Any idea where does it really comes from? I have had a world of grief with SQL Server Express. I just followed you video step by step. Two things were different: 1. I got a failure on the reporting services, which I didn't need so I backed them out. 2. I do success on the reset BUT when I went to the Mngt Studio I don't the "Database type filled in or the Database server name. This was the same problem I have seen with each install. Any ideas??? This was a great video!!! /DaveS

By the way, one of the reasons that I am doing the upgrade now is that PowerDNN upgraded their SQL servers to 2008 and when I download backups from them I can't install the database with SQL Server 2005. Yuk! So it was make either make the switch to Windows7 OR install a whole mess of required components to XP.

/DaveS

I'm not sure where "Classic.Net App Pool" came from. I did not make any special configurations before the video, the video is to a barebones windows 7 install so it should match up.

The one thing I did do before attempting to install anything was install updates for windows 7. After installing SQL Server I would also apply any updates.

Also, one thing to think about, I have Windows 7 (64bit) running on my main machine + then I have virtual PCs with XP, Vista and Windows 7 (32bit) - Installing DNN to a virtual PC makes it much easier if you need to start again for instance if SQL Server does not install correctly.

Thanks,

Any idea about the SQL Mngt Studio not being able to find the databases? In the services rhey "appear" to have been started.

Not sure, I would have a look at some SQL forums and see if they have any tips on corrupt SQL installations

As "stupid" as this sounds this was sollved by typing in the name of the instance 'DSnow2\SqlExpress' to SQL Mngt Sdudio to make the connection.  Why Lee's computer can find the default instance and mine can't I do not know.

Power DNN changed from SQL 2005 servers to SQL 2008 servers around 2/14/10. The effect of this on me was then when I tried to download and restore a copy of my site on my localhost I got obscure Transact SQL errors from SQL Mngt Studio during the restore.  I also had to ungrade to SQL 2008, which has many prerequisites.  

I thought that this was a good time to upgrade to Windows 7 Pro 64 bit which had all the prerequisites.

The Issue51 video was a great help! Since my database isn't stored inside of the DNN file-space and I require access vis SQL Mngt Express I had some additional steps. 

The most interesting one was that I had to use SQL Mngt Studio to add 'IIS APPPOOL\Cl ic .NET AppPool' as a user and give it dq_owner rights.  I guest that this is the ASPNET user from the IIS that shipped with XP.

Anyway I am running on the new configuration, so I can start my current localhost errors.  Something is eating the 'Cl ic space .Net space AppPool a couple lines above.

/DaveS

hi,how can i download this video?is it free or i should pay for that?

You need to purchase a subscription to DNNCreative Magazine.

I followed the first three video tutorials for enabling IIS and installing the SQL Server Express 2008 with Advanced Services and downloading DNN. After I created the folder for the DNN site, the 5.02.04 version, I attempted to install it from the web. I recived the error HTTP Error 401.3 - Unauthorized You do not have permission to view this directory or page because of the access control list (ACL) configuration or encryption settings for this resource on the Web server. I double checked the permissions on the files, and they are exactly as suggested in the video. Do you have any suggestions for troubleshooting this? I am a complete beginner in working with this system.

Do you see any part of the installation wizard, or does this happen immediately when you attempt to browse to the site?

It's obviously a web server configuration problem.  What is the operating system and IIS version?

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.

EDIT: OK, The video3 makes an assumption that IIS is using DefaultAppPool. For those not installing on a fresh install off IIS, and having permission issues... read on.


I believe the video is technically incorrect for assigning app pool and file permissions. The two combinations are mismatch.

When creating the site in IIS 7.5 your application pool should match the user permissions given write access to the root folder. In the video we are instructed to choose "Classic .NET AppPool". We are then instructed to add the user "IIS AppPool\DefaultAppPool" which leads to "DefaultAppPool".

This will only work if IIS is set up globally to set The Default DefaultAppPool. So a notation should be added the the Identity needs to be set to DefaultAppPool inside the Application Pool Advanced Settings.

More correctly for utilizing the granular permission introduced with IIS 7.5 would be to keep the name assigned by IIS for Application Pool to match your new site.

I believe it should be application pool = mynewsitePool, then you can add the user permission to the root folder by typing IIs AppPool\mynewsitePool.

A little better explanation: Here.

I was also confused why the app pool selected under permissions did not match the app pool assigned to the application. I just used defaultappPool instead of the clasic.net, and it works. I then went a step further and created a dedicated app pool for the site. As you say, as long as permissions for the app pool are assigned to the folder, it works great. Maybe a bit more could have been said on this topic.

In the videos Lee shows 2 different options of installing the database. The first option has DNN install it in the appData folder within the application. The second option is to create it manually from SQL management studio.

I tried both to make sure I could get them both to work. Success. I do have a question about when you would use one method vs the other.

Also if I was to create a site with the first method, is there a way to change the site over to the other way?

Is there a detailed SQL video on here?

Thanks Lee. The videos are great. I just wish I didnt wait 4 years to finally sign up for the magazine.

I personally prefer the option of having a database set up in SQL Server.

I assume that there are ways to move from one to the other, but I've never tried it.

And ... welcome to subscribership!

Hi there,

suddenly i have the installation error on all dnn versions both in WVD and in Web Matrix:
Connection Error(s):
Index #: 0
Source: .Net SqlClient Data Provider
Class: 11
Number: 4064
Message: Cannot open user default database. Login failed.

Index #: 1
Source: .Net SqlClient Data Provider
Class: 14
Number: 18456
Message: Login failed for user 'SOFT2\ASPNET'.

and it was also disaibled "auto" option with dnn install.

well, looked in bunch of online solutions, but basically, as i am using and dnn, and sql and Vs, WVD and Matrix for years, all solutions pointed on various things - but solution i actully very simple: if you have upgrade sql to sp3 - just simple uninstall that particular update, and dnn will run as always (with "auto" option) in VS, WVD and Matrix.

den

Thanks for this uptated series on creating a localhost site in Windows 7. However, the seires on moving it to a hosting provider is pretty outdated (2007) and, as a result, I have not been successful in moving my site to a hosting provider (Domain.com).

I used this tutorial to create a local host website on Windows 7 virtualbox. I know want to move it to Domain.com so that others can work on it with me. The DNNCreative tutorial for this is from 2007- oudated. I tried to use it anyway without success. Do you guys have any newer how to's for this?

I used this tutorial to create a localhost site on Windows 7 virtualbox. I now want to move it to Domain.com so that others can log in and work on it. However, your tutuorial "how to transfer a localhost to live site" is from 2007- outdated. I tried to apply it anyway without success. Do you have any how to into. for moving the latest version of DNN from localhost to Domain.com?

I can't give you specific instructions for Domain.com, but his is the basic process.

1. If you know the domain you will be using on the domain.com site, go to Site Settings and add a Portal Alias for each portal. Use the domain you will have at domain.com.
2. Make a backup of your database using SQL Server Management Studio
3. Copy the backup to domain.com and "restore" it to your SQL Server.
4. Copy all of your files from your local installation of DotNetNuke to the root directory of your domain.com site.
5. Edit web.config to alter the configuration strings (there are 2 of them) for the SQL Server that you are using.

That should be it. If you didn't do step 1, you can add a portal alias to the PortalAlias table in the database using SQL Server Management Studio.

If all of the above scares you, you might be better off using the Evotiva Backup module. You install it on your local site and use it to create two files (we have a tutorial DNNBackup Module for DotNetNuke for that module). You then upload those two files and a Restore Pack to your domain.com site. Then, you can browse to the site to restore your DNN Installation and do all of the configuration you need from a web browser.

And ... you should be able to get competent support from domain.com in doing the transfer. If you can't, you should shop around for a hosting company that knows DotNetNuke!

Hi Joe,

OK, I did step 1. portal alias. I misunderstood 2 & 3 from the tutorial and was past this when I realized so I did not get this done. However, that should not impact whether the site runs at Domain.com, correct? I did step 4 to the wwwroot folder at Domain and all files transferred successfully. I did Step 5 but I'm not sure that it is correct. I did this via the tutorial but it was outdated so I had to wing some things a little. I think I did it right but do you have specific info on this step or how I can check that it is correct? You can type the address www.artisan4u.com to see the error that currently comes up. Thanks for your help, David

Steps 2 and 3 are crucial, as that's where all of your content is stored.

Thanks Joe, it looks like I'll have to restore my Domain.com site and start from scratch with your tips above. Since you guys promote using localhost and have a newer tutorial on building it with Windows 7, it would be good if you updated the series on how to move it to a live service provider. I will try the backup program you recommend and agree it makes sense to move to a provider who is more DNN friendly. Network Solutions was pretty good with service; Domain.com has been unresponisive and from what I have read, I think I will try 3essentials.

Laura,

These days I am using xxx.dnndev.me as the domain name for my test sites.

dnndev.me is a domain name that was created by a member of the DotNetNuke community. It "resolves" to the localhost address. This permits you to create sites like bob.dnndev.me, etc and not have to worry about adjusting the hosts file. It also solves the problem of having local sites in subdirectories.

The idea of updating installation videos is a good one, but I will repeat that the existing tutorials are quite good and not inaccurate.