It appears that when I copied up the 5.2 upgrade all the files were apparently not FTPed correctly before the install kicked off.  I've re-copied all the files and now I get...

[FileLoadException: Could not load file or assembly 'DotNetNuke.Membership.DataProvider' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)]
   System.Reflection.Assembly._nLoad(AssemblyName fileName, String codeBase, Evidence assemblySecurity, Assembly locationHint, StackCrawlMark& stackMark, Boolean throwOnFileNotFound, Boolean forIntrospection) +0
   System.Reflection.Assembly.nLoad(AssemblyName fileName, String codeBase, Evidence assemblySecurity, Assembly locationHint, StackCrawlMark& stackMark, Boolean throwOnFileNotFound, Boolean forIntrospection) +43
   System.Reflection.Assembly.InternalLoad(AssemblyName assemblyRef, Evidence assemblySecurity, StackCrawlMark& stackMark, Boolean forIntrospection) +127
   System.Reflection.Assembly.InternalLoad(String assemblyString, Evidence assemblySecurity, StackCrawlMark& stackMark, Boolean forIntrospection) +142
   System.Reflection.Assembly.Load(String assemblyString) +28
   System.Web.Configuration.CompilationSection.LoadAssemblyHelper(String assemblyName, Boolean starDirective) +46
 

Is there any way to force the install script to run again?

Could this something else altogether?  Please help.  My production server is down...

Thanks!

Ian

I finally resorted to restoring a backup and re-applying the 5.2.  Now, I'm getting the following where most modules would normally be...

Error: Products is currently unavailable.
DotNetNuke.Services.Exceptions.ModuleLoadException: The type initializer for 'DotNetNuke.Modules.Html.DataProvider' threw an exception. ---> System.TypeInitializationException: The type initializer for 'DotNetNuke.Modules.Html.DataProvider' threw an exception. ---> System.InvalidCastException: Unable to cast object of type 'DotNetNuke.Modules.HTML.SqlDataProvider' to type 'DotNetNuke.Modules.Html.DataProvider'. at DotNetNuke.Modules.Html.DataProvider.CreateProvider() at DotNetNuke.Modules.Html.DataProvider..cctor() --- End of inner exception stack trace --- at DotNetNuke.Modules.Html.DataProvider.Instance() at DotNetNuke.Modules.Html.WorkflowStateController.GetWorkflows(Int32 PortalID) at DotNetNuke.Modules.Html.HtmlTextController.GetWorkflowID(Int32 ModuleID, Int32 PortalID) at DotNetNuke.Modules.Html.HtmlModule.Page_Init(Object sender, EventArgs e) --- End of inner exception stack trace ---

Any more ideas?

Thanks!

Ian

DotNetNuke.Modules.Html.SqlDataProvider.dll doesn't exist in my bin folder.

The site was first installed in 2005...  I'm not sure which version.  2.x?  This has been a two-part upgrade.  I started from 4.9.? and upgraded to 5.1.4 (which never really worked correctly) then in an attempt to correct it, I went ahead and upgraded to 5.2 which was released during my debugging of the former upgrade.

Now I fear that I'm in a situation where I'm going to have to start from scratch.  I really hope this is not the case.  DNN will lose some substantial cred with me if this is the case.