Between your attempt to back out of the first upgrade, the incorrect changes to web.config made while trying to turn off customErrors, and now the swapping of web.config files between the failed site and a different site, I'm afraid that you may have not only a really messed up site (or perhaps sites as the swap of web.config files with that of a different site may have also messed up the database of the other site) but database as well.

Is there any possibility that GoDaddy can restore both the files of the failed site AND the site's database to that existing before the failed update? Did you make any backup of either files or database yourself before attempting the upgrade?

If that is not possible, we will have to try to correct the changes you made to the web.config then set customErrors mode="Off" to try to track down the original error. Note that mode="Off" is case sensitive - capital 'O' and lowercase 'ff'. I did notice just now that your site is back to showing the error you first reported.

In the meanwhile, please do NOT make any other web.config changes or swap web.config files between sites!

---

Bill, WESNet Designs
Team Lead - DotNetNuke Gallery Module Project (Not Actively Being Developed)
Extensions Forge Projects . . .
Current: UserExport, ContentDeJour, ePrayer, DNN NewsTicker, By Invitation
Coming Soon: FRBO-For Rent By Owner

I've got great news, I got it, with your help and direction, I got it! I cannot thank you enough for the help!

 What I did was, after taking your advice and trying to change the atributes for the web.config file, It was not working, so I brought up the file with the problem and the one from the site that works and compared the two. I was not able to see any differences between the two except for the different codes for the redirects. I figured I don't have anything to loose at this point, So I copied and pasted the codes from the problem file to the good file and pasted it into the FTP for the problem site and it worked!

        Thanks again, Jeff...