Additional info; I made sure that the virtual directory on the new IIS machine is using ASP.NET 2.0. This is currently the only website on my new IIS machine, so I did not concern myself with assigning it its own application pool.
I have confirmed that both datebase connection strings within the new web.config point to the correct database, using the correct User ID and Pwd. BTW, the original web.config has only one connectionString= located within <appSettings>. It does not have a <connectionStrings> node.
Also, the original web.config does not have encryption keys. It does have codeSubdirectories and I copied the DataBaseOwner and ObjectQualifier keys to the new web.config, but I find no encryption keys in the original web.config. And it has no machinekey either.
More Background: During the install of DNN 5.1.1, the Installwizard.aspx seemed to enter some sort of infinite loop, where it repeatedly displayed Undefined:Success. While this was occurring, I found several suggestions within the forums to run Install.aspx instead of InstallWizard.aspx. I got much better results with Install.aspx. Most installation components were successful, but I got about a dozen error logs that ranged from 02.02.01.log to 05.01.01.log. I went thru each error log yesterday, fixing whatever the log reported as being wrong. I then ran Install.aspx again and it generated about 3 more error logs and I fixed the problems that were reported by those logs as well. I ran Install.aspx a third time and it displayed the message like Installation Complete, and it also displayed a hyperlink that read Click here to enter your portal. And that is where I am currently at. I am viewing the root of my portal (Default.aspx), which looks exactly like the home page on the old, original DNN website, except that on this new site, I have boxes for entering Username and Passwords, but it excepts no names or passwords that I enter. As soon as I click the Logon button, it clears out the username and password that was entered, and waits for me to reenter another username and password (BTW, if I go back and try to run Install.aspx again, I simply get a blank page).
I really don't want to install DNN 5.1.1 directly over top the original website, b/c it is a production site that is used daily by employees. If that site is down during business hours, I will be in big trouble. If I had a better understanding with what I was doing, I would wait and come in on Saturday, and upgrade the site to DNN 5.1.1. But at this point, I don't feel confident that I could have the site back up and running by Monday morning.
I've been exposed to DNN for one full week now and I'm really stumped on what to do next. Should I wipe out the test environment on my new IIS machine and start over? If so, what should I do differently? I went thru the following guides and I don't think I overlooked anything:
http://www.dotnetnuke.com/Community/Blogs/tabid/825/EntryId/1228/This-is-how-I-upgrade-a-DNN-instance.aspx
http://www.dotnetnuke.com/Community/Blogs/tabid/825/EntryId/1459/Upgrading-DotNetNuke.aspx
http://www.deutschnetnuke.de/AboutDotnetNuke/V3V4TippsTricks/Upgradedurchführen.aspx