I just finished running the upgrade from 6,00.02 to 6.01 and received some error messages.

00:04:58.954 -   Installing Package File AspNetMembershipProvider_06.00.02_Install:  Error!

00:05:59.219 -   Installing Package File MemoryModuleCachingProvider_06.00.02_Install:  Error!

00:05:59.219 -   Installing Package File MemoryModuleCachingProvider_06.00.02_Install:  Error!

00:07:18.985 -   Installing Package File SolpartMenuNavigationProvider_06.00.02_Install:  Error!

I'm still new to DNN and am not sure how serious these errors are or how to go about correcting them.  My site comes up and I can log in as the Super User.  The Membership Provider error especially concerns me because that is my next area of exploration.  I seem to be able to do the few basic edits I tried to test the upgrade but I need some advice as to the seriousness of the errors and guidance in correcting them.  Thanx in advance.

Hmmm.  Don't misunderstand, I appreciate that you took the time to answer, but the cure might be as problematic as the disease.   When nobody answered I kept on poking around and discovered that the basic functionality seemed to be intact with the exception of the blog module.  I kept working and making changes.  Going back to the backup now is sort of a nightmare and a pain in the . . . !  It would also help to understand how the permissions can be changed between upgrades?  I ran the 6.00.00, 6.00.01, and 6.00.02 upgrades with no problems and never gave a thought to the base line permissions. Presumably going back to the backup would be a prelude to rerunning the 6.01 upgrade again.  That begs the question, what should I do, if anything, before rerunning the upgrade to ensure a clean result?  Wordpress is looking better everyday :-(

Sometimes the tail wags the dog.  In trying to solve this problem and get the blog module working I've managed to corrupt the application and now it won't boot.  I rolled in my backup from a few days ago and THAT wouldn't work.  I have the site hosted with Godaddy and they are substantially below useless when it comes to troubleshooting DNN.  It appeared likely that I would have to start all over from scratch.  I then decided to do something I came close to doing when I first considered revisiting DNN.  I decided to find a hoster who cared about DNN and could help out in a pinch.  It came down to PowerDNN and 3Essentials and I went with 3Essentials.  Stay tuned.