In upgrading a test site, I had this same issue.

I restored backups of both the database, and the files.

Extracted the upgrade file over the test site

Removed old DNNProvider

Install runs, but I received the an error on returning to the site.  I discovered that this related to using House of Nuke's HouseMenu 2 (beta).

I have removed the offending code from my template, and the page now displays properly (albeit, without the menu).

I now have had two separate issues:

1.  My current issue is that it will not allow me to log in.
2.  My previous issue was that, it would allow me to log in, but when I tried to access admin pages, it would throw an error.  I don't have the replication of that error, as I reverted to the old version, to attempt the upgrade again.

I am attempting to figure out the issues related to this, I will post more as I know it.  And if anyone has any suggestions, I would be most appreciative!

Thanks,

Alex

I got past the provider dll error when I found a newer version installed in a subfolder and renamed the original.  Next was an error on pageblaster, which I commented out in web.config.  Then upgrade scripts started to run with the following feedback:

Upgrading DotNetNuke
Current Assembly Version: 05.00.00
Current Database Version: 04.08.04

Upgrade Status Report
00:00:00.062 - Upgrading to Version: 5.0.0
00:00:00.592 -   Executing Script: 04.09.00.SqlDataProvider Success
00:00:14.149 -   Executing Script: 05.00.00.SqlDataProvider Error! (see 05.00.00.log for more information)
00:01:12.199 - Performing General Upgrades
00:01:23.181 - Installing Optional Modules:
00:01:23.197 - Installing Optional Skins:
00:01:23.213 - Installing Optional Containers:
00:01:23.244 - Installing Optional Languages:
00:01:23.259 - Installing Optional Providers:
00:01:23.306 -   Installing Package File AspNetMembershipProvider_05.00.00_Install:  Success
00:01:25.178 -   Installing Package File DatabaseLoggingProvider_05.00.00_Install:  Success
00:01:25.724 -   Installing Package File DNNMembershipProvider_05.00.00_Install:  Success
00:01:26.223 -   Installing Package File DNNMenuNavigationProvider_05.00.00_Install:  Success
00:01:26.879 -   Installing Package File DNNTreeNavigationProvider_05.00.00_Install:  Success
00:01:27.378 -   Installing Package File FckHtmlEditorProvider_02.00.02_Install:  Success
00:02:15.115 -   Installing Package File FileBasedCachingProvider_05.00.00_Install:  Success
00:02:15.693 -   Installing Package File SchedulingProvider_05.00.00_Install:  Success
00:02:16.223 -   Installing Package File SearchIndexProvider_05.00.00_Install:  Success
00:02:16.800 -   Installing Package File SearchProvider_05.00.00_Install:  Success
00:02:19.421 -   Installing Package File SolpartMenuNavigationProvider_05.00.00_Install:  Success
00:02:21.122 - Installing Optional AuthSystems:
00:02:21.137 -   Installing Package File LiveID_01.00.01_Install:  Success
00:02:23.196 -   Installing Package File OpenID_02.00.00_Install:  Success
00:02:24.429 - Installing Optional Packages:

Upgrade Complete

I don't know why the 4.9 script ran as I was running 4.9 not 4.8.4.

I accessed the log which had the following message:

Error: Cannot insert duplicate key row in object 'dbo.Packages' with unique index 'IX_Packages'.
The statement has been terminated.

The end result so far is this:  Portals are accessable, but really slow.  I uncommented PageBlaster and it appears to run fine, but all is still slow.  A couple of modules are broken, but can't figure out why.  Hoping once I figure out which upgrade scripts didn't run and I can determine how to make them run I can solve most of the problems.  Inventua Shadow won't run.  Ifinity's url master which was disabled throws an error when you access it's setup page.  Icons are missing in admin and host for those and some other modules.  Options are missing from the bottoms of some tabs, for instance, no option to add a new portal or install an additional module.  I'm open to suggestions (other than fresh start as I don't have to ask to figure that one out!)

D

When install finally ran, I did have it completely off.  Prior that I never reached the install.aspx file.