I'm trying to upgrade a site from DNN 4.8.0 straight to DNN 5.2.1. However, i am getting some very strange errors. I was curious if i should follow a different upgrade path? Such as upgrade to DNN 4.9.5 then upgrade to 5.2.1 or perhaps i should transfer my info from web.config to release.config and rename it appropriately so that i'm starting off fresh? I'm curious if using the same web.config and hoping that DNN 5.2.1 can update it successfully is having some issues? I've done this upgrade 2 times in a row and produces the exact same errors. These errors are: ------------------------------------------------ 1) The Upgrade Status Report process showed Success except for the following: Updating Config Files: 05.01.00 Error! Updating Config Files: 05.02.00 Error! Updating Config Files: 05.02.01 Error! Installing Package File FileModuleCachingProvider_05.02.01_Install: Error! Installing Package File MemoryModuleCachingProvider_05.02.01_Install: Error! --------------------- 2) After i continue to website, Page does not display skin properly, it shows the skin and containters but no TEXTHTML content. However the content shows up when i login as host. Each page also displays"Critical Error Has Occurred" Next to the empty containers. ------------------------------- 3) Issue is when i try to access the new Host Settings. I get the following error on the screen. ******************************************* Error: Host Settings is currently unavailable. DotNetNuke.Services.Exceptions.ModuleLoadException: C:\Inetpub\mysite\WebSites\DesktopModules\Admin\HostSettings\HostSettings.ascx.vb(309): error BC30198: ')' expected. ---> System.Web.HttpCompileException: C:\Inetpub\mysite\WebSites\DesktopModules\Admin\HostSettings\HostSettings.ascx.vb(309): error BC30198: ')' expected. 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 --- Any tips or suggestions would be great on helping me out of this mess i'm in. Fortunately i've backed everything up and will try the upgrade a 3rd time. I have not idea what is going wrong. Anyone in the forum. Please Advise with suggestions.

First, make sure that you have the correct configuration for DotNetNuke 5.2.1. Specifically, you need to have SQL Server 2005 or above and .NET 3.5 SP1.

If you have that and it is still failing, I would suggest that you upgrade to 4.9.5 first, and then to 5.2.1. Do not try to merge old and new web.config files. Just extract that upgrade package on top of the existing installation.

Thank you,
I just checked and i am currently using .NET 3.5 SP1.
The upgrade path of 4.9.5 sounds more sensible. I will try that and let the forum know how it works out. Plus I'll transfer my SQL 2005 and Machine Key info over to the release.config then rename the release.config to new web.config and start the process from there. Really appreciate DNN Creative's rapid response.

YES!!! THAT WORKED!... It is best that when you're making such a huge jump in versions, to break your upgrade down. The best path for upgrading from DNN 4.8.0 is first to upgrade to DNN 4.9.5 (MAKE SURE YOU COPY YOUR SQL INFO AND MACHINE KEY to the upgrade file of release.config and rename it to web.config) Also be sure to back up all config and DNN files! Thanks for suggesting to take the 4.9.5 route... My site is now running DNN 5.2.1 after being stuck in DNN 4.8.0 Special Thanks to the Nuke Master IV

Super!

I ad the same problem and replacing the web.config with the DNN 5.2.2 release.config but passing correct values for machineKey validationKey and decryptionKey as well as db access parameters did the trick for me. I didn't have to upgrade in phases

Yes, it will vary for some and their setups... but after trying 4 straight galactic leaps to 5.2.1 and hitting an asteroid in my flight path... the calculated upgrade path in steps worked for us and several of other sites. I'll recommend that cautious calculated approach every time.