I would not try to revert to 5.0.0, but actually get 5.0.1 running. You could try the following:

• copy files of dnn 5.0.1 over your site
• try to run
• in case of errors try to run the 501 upgrade sql script manually (found in /providers/dataproviders/sqldataprovider/). Best run from sql management studio, but you have to remember when doing that to replace {databaseOwner} by dbo. and {objectQualifier} by the object qualifier you used (which is probably nothing...)
• recycle application pool
• try to run again

if all else fails.. get an expert to look at it (if you need my help, mail me at support@apollo-software.nl, not free though...)

about not being able to rollback an installation: that is extremely difficult, since changes to files and database are permanent. Even though we could device a way to backup the databse prior to the upgrade, doing a backup of the files is not possible given the current way to do the upgrade (copying over the old version). We have been talking about enhancements to the installer in such a way that the installer would be able to download the upgrade files and run the upgrade from there, but thats something for a far far far future.... so until then.. we have to do with what we have.

Hopefully the person that messed up the site in the first place learned his lesson and will never do that again.. in fact.. making mistakes is one of the best ways of becoming an expert (i say this from experience :) )

DNN Blog | Twitter: @erikvb | LinkedIn:

Yeah, That was one of the first things I tried. When I saw the install folder I started to open the various pages directly in my browser hoping it would trigger an install. Unfortunately all I get doing that is an XML errror: 

XML Parsing Error: no element found
 

I'm going to keep hammering away at it and try and get 5.0.1. working. Right now I can't even login to the website. When I try logging in, I get the following error: 

A critical error has occurred.
Parameter count does not match Parameter Value count.

Unfortunately, it doesn't tell me which stored procedure is mucked.

What I'm doing right now is trying to compare databases. I created a separate DB and did a fresh install of 5.0.0 to a separate website. Then I did an upgrade to 5.0.1. I'm using a DB compare tool to try and compare that install against our production one to see what's different. Unfortunately, our production install also has a bunch of Desktop Modules installed, so now I need to go through those and install them on the test site so I can get these two DB's as close as possible. Maybe then I can find out what's actually different between them and diagnose where the problem is.

Chris,

Just wanted to drop in and thank you, your advice about uploading the DLL's from a fresh install was spot on, i had the same problem - i compared the fresh 5.0.1 DLL's and what was left after the upgrade, some, including the relevant providers were of a different file size.

Perhaps of note: I run a local test webserver on IIS6 and SQL2005. I only just last week migrated my installation to a new webhost on IIS7. So barring server platform differences, the files and database were identical. I installed the upgrade on my test server - worked perfectly so i went ahead with the upgrade on the remote server - bam, same issue as you. I wonder if its permissions related (at least for me), as my remote ugprade was initially stalled by permisssions errors that i had to have the technicaly support team fix. It does seem unlike that only some DLL's would not have had their permissions updated, though i dont know how many of the dll's actually changed with 5.0.1.

Charles