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.