Wow.... that really doesn't look like my comments.
1) I don't know whether I am using integrated security or not. I don't even know what that is.

2) I understand the two forms. I think I did that perfectly

3)I see the two locations. I will try to paste those sections again:

The section I am trying to paste won't stay pasted.

According to SSMSE, I am connected to my database and I am connected via SQL Authentication. The userID even says it's the DBO

I think that I am going to have to vote "stumped." It "seems" that you are doing all of the right things, yet something clearly is wrong.

Is this a brand new installation?

If it is, it might be time to delete the database, delete the web directory and start over.


I'm guessing that you haven't even gotten to the part where you see the installation wizard. Is that correct? If you did, you should have been able to check file permissions and check the database connection.

Yeah ... start over from scratch if this is a new installation.

Joe,

I think I am going to do two things:

1) I am going to start all over.
2) I am going to use a machine that has a clean Vista OS (mine has all kinds of stuff on it)

I do want to clarify one issue for you. I was successful initially with a DNN 5.0 fresh install on this Vista box (the db stuff was pretty much automatic). That install does not work any longer.

After I proved to myself that I could get a local DNN application running, I tried to bring a copy of my production site (multiple parents and a child portal) from DNN4.8.4 (I think) over. That NEVER ran successfully and it screwed up my fresh install of DNN 5.0.

Lastly, Lee sent me a note yesterday...indicating that I could attach screen shots, but I cannot see any functionality that allows that here (I see ActiveForums 3.7 below).

I do have ONE additional line of questioning. Would it be easier for me to use Visual Web Devoper Studio Express to get these localhosts running? I have just downloaded the 2008 version (since I see Lee use it in his tutorials...I like his references to the colors...to make sure I am doing it right). Is that the right version?

No.  Stay away from Visual Web Developer unless you are going to build modules.

Get DotNetNuke running as a web site.  Start with the install version and start with a new and empty database.

Joe,

All the tutorials show Lee editing the web.config file with VWD. I was thinking that Could reduce the possibility of error on my part. Also, I thought that tool has some diagnostic stuff related to database connections (I can do the content stuff, it's the db and ISS that seem to throw my non-CS mindset).

So, if I respectfully reject your advise (on this topic), which version would I use?

Since you are using a "modern" version of DotNetNuke, you may never have to edit the web.config file.

The diagnostic stuff is part of the DotNetNuke installation wizard.

I have DNN versions and DBs going back to early 4 (4.0.1, if my first I think). The only version I haven't had to edit the web.config, so far, was the fresh install of DNN5.0 on my localhost, but I will need to alter that to upgrade my production site, correct?

I was actually referring to the need to "merge" data from the old web.config into the new one when doing an upgrade.

Upgrading from versions 4.6.2 and higher no longer require that you do it.  Just unzip the upgrade release on top of your web directory and then browse to your site to upgrade.

When you move your 5.x site (or any other site) from development to a live server, you'll still have to edit the connection strings to point to the live site's database server.  You won't have to copy machine keys or other items.

[Note to me and to others who may know more about this:  I did recently see an example in which the connection strings were stored in a separate file.  I need to figure out how to do this!]

Is this a brand new installation?

If it is, it might be time to delete the database, delete the web directory and start over.

The new install was just a proof step. My goal is to get a production site running locally. I can delete the restored db. Exactly what is composed of "the web directory."

d

The "web directory" is the directory into which you copied the DotNetNuke files. It's also the directory that is the directory specified for the website in the IIS configuration.

Joe,

Taking your advise, I deleted everything and started all over. It did take a bit of effort, but I have EVERYTHING running on my local host now....UNDER VISTA. The battle is over.

Two things worthy of recording.... Firstly, I noticed that my initial problems were the result of my original FTP download. That process was evidently interrupted at some point and I was missing the "Providers" folder. That must be called as part of the startup process and since it was not there, I saw the "This site is under construction" My learning...If I see that error, I am starting all over immediately.

Secondly, configuring a child portal is a little tricky (following the logic of Lee). On all the parents he named them by using the domainname+com, but a child looks like domainname+com/childname. So, even though DotNetNuke will allow you to create a PortalAlias with a "/", you cannot name the internet application with a forward slash in it under VISTA. And, I wasn't sure what directory to point to, since my ChildPortal had its data in a subdirectory of its parent. It took a bit, but I just gave the alias the name of the child and I pointed IIS to the root directory of the portal....AND, everything worked out.

Lastly, IIS under Vista and VISTA security is a bit different than the OS in the tutorial....with patience and persistence localhost sites are doable. DNN 5.0 and DNN 4.8.4 are running locally. I will upgrade everything to 5.0, add some custom modules and then see if I can push them out to the production site.

THANK YOU, so much!