Okay, I gave GoDaddy's "one click" install a try and go figure, it works fine without the error. Now, "why?" is my next question. Do they modify the files? During their automated install do they make setting changes that provide the proper permissions? I have had issues with their install of DotNetNuke before, especially during updating to newer versions of modules or the core, so I am not sure I want to stay with their install.

Maybe I will play more and see about removing the files without doing their automated uninstall of DNN. Then start the install process over again doing my own manual push of the files.

I think we all need to call GoDaddy and report this issue, maybe they will get the picture.

ok I have a solution. FINALLY! It sucks you have to do it this way but it works and is the only solution I've found.

 

• Start with a clean hosting account (if you have already tried to setup something up delete everything) - Make sure everything is gone including the database before you go on.  GoDaddy says wait 30 minutes after the deletion but I say that is bogus.  just make sure the database is gone (takes a couple of minutes). 
• in the Content tab go to "GoDaddy Hosting Connection" 
• go to the Content Management section and select DNN 
• Click the install button 
• Continue through the little wizard they have.  I use the subdirectory dnn for my install.   
• After the install is complete (takes a few minutes - status can be found in the hosting connection under My Applications) navigate in a web browser to that direcotry (www.yourdomain.com/dnn) 
• go through the setup as you normally would.  Godaddy fills in most fields for you. 
• Once the site is setup go back to the hosting control panel (not connection) and go to the File Manager under content.  
• navigate into your dnn sub directory.   
• change the number of items shown from 25 to 50 
• use the select all check mark to select all items in the list 
• click the copy button and select the html folder (your root) from the directory tree on the left then click ok 
• the copy will take a little while (go get a drink) 
• once the copy is done go to your sql database and login to the manager 
• Find the PortalAlias table and click browse 
• Click the edit pencil next to the 1 entry that should be in there. 
• in the HTTPAlias column remove the /dnn and save the changes 
• navigate to your new site www.yourdomain.com 

This is pieced together from a couple different installation solutions given to me by godaddy, and also a couple installation posts for different issues from the DNN Forums.  One post that showed me what needed to be changed for the database suggested to take your site offline by creating a app_offline.htm file at the root of the DNN installation.  If you do that step don't forget to remove it before you nagivate to your new site.  I didn't do that step since I knew no one would be looking at the site while I did this.