Greetings, Recently I upgraded from 4.9 to 5.14 after I saw there was an alert for a "Critical Update". I proceeded to update as I usually do and everything seemed to go well until I tried to access the host settings which is when I received the following errors: Error: Host Settings is currently unavailable. DotNetNuke.Services.Exceptions.ModuleLoadException: D:\DotNetNuke\DesktopModules\Admin\HostSettings\HostSettings.ascx.vb(268): error BC30456: 'IsWebFarm' is not a member of 'DotNetNuke.Entities.Host.ServerController'. ---> System.Web.HttpCompileException: D:\DotNetNuke\DesktopModules\Admin\HostSettings\HostSettings.ascx.vb(268): error BC30456: 'IsWebFarm' is not a member of 'DotNetNuke.Entities.Host.ServerController'. at System.Web.Compilation.BuildManager.CompileWebFile(VirtualPath virtualPath) at System.Web.Compilation.BuildManager.GetVPathBuildResultInternal(VirtualPath virtualPath, Boolean noBuild, Boolean allowCrossApp, Boolean allowBuildInPrecompile) at System.Web.Compilation.BuildManager.GetVPathBuildResultWithNoAssert(HttpContext context, VirtualPath virtualPath, Boolean noBuild, Boolean allowCrossApp, Boolean allowBuildInPrecompile) at System.Web.Compilation.BuildManager.GetVPathBuildResult(HttpContext context, VirtualPath virtualPath, Boolean noBuild, Boolean allowCrossApp, Boolean allowBuildInPrecompile) at System.Web.UI.TemplateControl.LoadControl(VirtualPath virtualPath) at System.Web.UI.TemplateControl.LoadControl(String virtualPath) at DotNetNuke.UI.ControlUtilities.LoadControl[T](TemplateControl containerControl, String ControlSrc) at DotNetNuke.UI.Modules.ModuleHost.LoadModuleControl() --- End of inner exception stack trace --- Upon checking the error log I received this entry. ModuleId: 327 ModuleDefId: 72 FriendlyName: Host Settings ModuleControlSource: DesktopModules/Admin/HostSettings/HostSettings.ascx AssemblyVersion: 5.1.4 PortalID: 0 PortalName: My Website UserID: 1 UserName: host ActiveTabID: 16 ActiveTabName: Host Settings RawURL: /tabid/16/portalid/0/Default.aspx AbsoluteURL: /Default.aspx AbsoluteURLReferrer: UserAgent: Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 6.1; WOW64; Trident/4.0; GTB6.3; SLCC2; .NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET CLR 3.0.30729; Media Center PC 6.0; .NET CLR 1.1.4322) DefaultDataProvider: DotNetNuke.Data.SqlDataProvider, DotNetNuke.SqlDataProvider ExceptionGUID: 56e7b314-a1c4-4726-ac29-34ef3666453b InnerException: D:\DotNetNuke\DesktopModules\Admin\HostSettings\HostSettings.ascx.vb(268): error BC30456: 'IsWebFarm' is not a member of 'DotNetNuke.Entities.Host.ServerController'. FileName: FileLineNumber: 0 FileColumnNumber: 0 Method: System.Web.Compilation.BuildManager.CompileWebFile StackTrace: Message: DotNetNuke.Services.Exceptions.ModuleLoadException: D:\DotNetNuke\DesktopModules\Admin\HostSettings\HostSettings.ascx.vb(268): error BC30456: 'IsWebFarm' is not a member of 'DotNetNuke.Entities.Host.ServerController'. ---> System.Web.HttpCompileException: D:\DotNetNuke\DesktopModules\Admin\HostSettings\HostSettings.ascx.vb(268): error BC30456: 'IsWebFarm' is not a member of 'DotNetNuke.Entities.Host.ServerController'. at System.Web.Compilation.BuildManager.CompileWebFile(VirtualPath virtualPath) at System.Web.Compilation.BuildManager.GetVPathBuildResultInternal(VirtualPath virtualPath, Boolean noBuild, Boolean allowCrossApp, Boolean allowBuildInPrecompile) at System.Web.Compilation.BuildManager.GetVPathBuildResultWithNoAssert(HttpContext context, VirtualPath virtualPath, Boolean noBuild, Boolean allowCrossApp, Boolean allowBuildInPrecompile) at System.Web.Compilation.BuildManager.GetVPathBuildResult(HttpContext context, VirtualPath virtualPath, Boolean noBuild, Boolean allowCrossApp, Boolean allowBuildInPrecompile) at System.Web.UI.TemplateControl.LoadControl(VirtualPath virtualPath) at System.Web.UI.TemplateControl.LoadControl(String virtualPath) at DotNetNuke.UI.ControlUtilities.LoadControl[T](TemplateControl containerControl, String ControlSrc) at DotNetNuke.UI.Modules.ModuleHost.LoadModuleControl() --- End of inner exception stack trace --- If anyone has any ideas as to what might have cause this I would be grateful for any advice. Thanks in advance. Rob

Were there any errors during the actual upgrade process?

The error message seems to imply that a dll did not get replaced.

You might want to revert to 4.9 and try again, this time looking for error messages.

Hi Joseph, Thank you for your reply. Sorry I haven't been able to respond quicker. My first attempt was to try and copy all of the DLL's from the 5.1.4 upgrade package to the correct folders and that did not work quite right and I'm turning up the same result. I then tried to revert back to 4.9.5 and that result was quite disasterous. I'm wondering if the way I am upgrading should be revised? I have never had issues until I tried the auto upgrade method. In previous successful upgrades I always edited the web.config and changed the connection strings, encryption keys, etc... If you have any thoughts I'd really appeciate to hear them. Thanks for your time. Rob

Since 4.6.2, you don't have to manually edit web.config.  That should make upgrading a simple process.

Were you not able to return to 4.9.5?  What happened when you did that?

Hi Joseph, This is the error I receive when I tried the upgrade: Compilation Error Description: An error occurred during the compilation of a resource required to service this request. Please review the following specific error details and modify your source code appropriately. Compiler Error Message: BC30451: Name 'ComponentFactory' is not declared. Source Error: Line 67: End If Line 68: Line 69: ComponentFactory.Container = New SimpleContainer() Line 70: Line 71: 'Install most Providers as Singleton LifeStyle Source File: D:\DotNetNuke\App_Code\Global.asax.vb Line: 69 Should I try to go back to 4.08.4? This is very perplexing! Thanks for the help. Rob

If there is a version of DotNetNuke to which you can safely revert, then I would do that first. 

Then, upgrade to 4.9.5.  Make a good backup of the database and web directory for that one, so that you can get back to 4.9.5.

Next, try the upgrade to 5.2.1.  Make sure first that you have SQL Server 2005 and ASP.NET 3.5 with SP1 installed, as these are necessary for 5.2.1.