I've been brought in to clean up an upgrade gone bad. I was hoping to get some guidance from the board here. We've got a bit of a tangled mess and I'm hoping for the best "path" to clean things up and get our site back in working order.

We've got a company website running DNN 5.0.0. An upgraded was attempted to 5.0.1. It appears the upgrade did not go well and something was done incorrectly, so my colleague tried to revert back to the previous version of DNN. I do not know how he accomplished this, but from the symptoms I've seen I think it's likely that he just copied the 5.0.0 files back over the 5.0.1 files in the InetPub folder.

The short of it is that after the "ugprade" process and "restore" to 5.0.0, the site started throwing errors (which I would expect, because the DB has changed, but unlike the code it was not reverted). In particular, the website complained that it was missing a pair of Stored Procedures (here's a link to the thread where my colleague was asking questions: http://www.dotnetnuke.com/Community/Forums/tabid/795/forumid/108/threadid/305189/scope/posts/Default.aspx).

I decided to follow Sebastian Leupold's advice. I grepped the SQL scripts and found the code to recreate both of those stored procedures. The presence of those procedures fixed some errors, but others are still persistent throughout the site. This continues to tell me that the DB had been modified to 5.0.1, but not restored to a previous 5.0.0. state.

What I noticed, grepping the SQL scripts, is that in the 5.0.1 script, those stored procedures are purposely deleted and never recreated. So my assumption is that for version 5.0.1 those SP's are not meant to be there.

It seems to me that we've got a mishmash - a smashup of 5.0.0 code coupled with a combo 5.0.0 and 5.0.1 database.

What I would like to do is revert everything back to 5.0.0 and then try and perform the upgrade to 5.0.1 after backing everything up. Or if there's no other option, install 5.0.1 and get it working. But I am unsure exactly how to go about this and not destroy our website.

Does anyone have any advice, suggestions on how to best go about fixing our problem here? 

Thanks,

Chris

Yes, I am aware. These are not my decisions to make. My own personal policy is to never install into a production environment a "beta" or "rtm" or "rc" application/framework. But again, not my decision. 

Unfortunately there is no valid backup prior to the upgrade because the person who did the upgrade foolishly put the backup files in the same directory as the automated backups, so it got overwritten a couple days later (brilliant, huh?)

At this point in time I don't know what to do. It seems like our website is completely screwed. I can't find any way to force DNN to run the upgrade process again. It seems like DDN is setup so that you have to do everything perfectly during an upgrade - a one shot process - and if you screw it up you're toast. Goodbye website.

The only thing I can think to do now is a completely fresh install of 5.0.1, and then try and copy the data table-by-table from the old database. Then I have to fix stylesheets, images... this could go on for days.

Incredibly frustrating.