Thanks, Matthias, for your feedback and for the link to the video. I did watch the video, but alas, no new news for me. This site is at a hosting provider, so I have checked and double checked the permissions for the folders and for the SQL server.

Since this hosting provider does not permit write permissions in the wwwroot directory, I have made a www directory with in that and given it write permissions, and also set it as a virtual directory. I have also made a DNS alias to the www directory. I have tried installing in different ways, such as directly to the DNS alias and also through the IPADDRESS/www url. Both approaches give the same results with the browser showing page errors as described above, and the Login link not working.

I'm sure it must be something simple like a conflict in the XML space or a JQuery problem, but I can't find it.

Thanks for all the suggestions, Matthias. Yes, I have been deleting and recreating the database for each new try. I have uploaded the install files into another private directory on the server so I can just have the server copy them over after I delete the site files at the end of a try.

I got really excited when I checked the config.sys file and found that the second connection string (the add key for SQL 2005 legacy module compatibility) was commented out. However, fixing it and doing a new install did not change the results. I checked the list of Users on the database and dbo is listed as one of the users. Do you think I should try changing the config.sys to be the main database user? If so, do I just change dbo to the username? What about the user's password... does that go into the config.sys at all?

I do have the virtual directory set up as you specified, it's actually IPADDRESS/www  where www is the name of my virtual directory. I have given that directory read and write permissions. That's good news about Plesk 9.5.2 supporting root directory write permissioning. I will pass that on to my hosting service, since they use Plesk.

One thing I did notice is that on the website configuration screen of the Plesk control panel it shows ISAPI_Rewrite support as Unavailable. I notice that after reloading the site files and recreating the database, when I type in the URL for the site, the DNN InstallWizard sceen that comes up has the same web page errors that I am getting on the home page. That wizard page comes up before it does any tests about directory permissions or database availability. I cannot proceed with the wizard because of these web page errors, like javascript errors. So I am starting to think the problem might be not in the config.sys file but in the environment. However, I cannot think of what else it could be. I am not sure whether ISAPI_Rewite support is necessary, but I am thinking it could be something like that.

Any more ideas? I could give you the site address if you are interested, since at this point it is just a test site, until I get it up and running.

Thanks for your thoughts.

I am not certain that I am using Plesk for permissions management. The hosting provider does offer Parallels Plesk SiteBuilder as an option for building a site, so I am presuming they use Plesk for the rest of it. (Since I have tried to do this install about 20 times, I have tried both with and without Plesk Sitebuilder managing the directory. I am currently without it.)

The File Manager app allows me to set permissions on the virtual sub-directory, www, for read, write, and execute. I have set those permissions for the only three types of users shown:
Application pool identity account      
Anonymous Web user      
Authenticated FTP user

I have changed the config.sys for the SqlDataProvider to be the database username instead of dbo. When I ran the install, I got the exact same results.

I think the database access must be okay because each time I do this, I check the database after the install and all the tables have been generated, along with roles, etc.

The problem seems to be that the browser can't get the right libraries, or something like that. If you want to have a look at the errors yourself, try http://atriumsystems.ourhosting.com/www/

The same errors show in both IE and Firefox. For example, it says that "Type is not defined" in Line 2 of h**p://atriumsystems.ourhosting.com/www/js/dnn.js
Well, the code for that seems to be Type.registerNamespace('dnn'); .

So, how could Type not be defined?

I think the code samples I showed in previous messages above were just for the line numbers in the page html code, while they should have been for the line numbers in the .js files that were referenced. The FireBug tool bar in Firefox makes this more apparent than the IE error display.