After upgrading from 4.3.5 to 4.4.1, I'm having skin problems on many pages.  I've also upgraded a couple of modules recently.  So I'm not 100% sure where the problem was introduced.  But I'm hoping someone can help me resolve it.

I would post the errors from the Event Log, but I get an error when I go to my Event Log.  Here is that error:

Error: Log Viewer is currently unavailable.
DotNetNuke.Services.Exceptions.ModuleLoadException: External component has thrown an exception. ---> System.Web.HttpCompileException: External component has thrown an exception. at System.Web.Compilation.AssemblyBuilder.Compile() at System.Web.Compilation.BuildProvidersCompiler.PerformBuild() 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.UI.TemplateControl.LoadControl(VirtualPath virtualPath) at System.Web.UI.TemplateControl.LoadControl(String virtualPath) at DotNetNuke.UI.Skins.Skin.InjectModule(Control objPane, ModuleInfo objModule, PortalSettings PortalSettings) --- End of inner exception stack trace ---

All of the errors I get on various modules are ModuleLoadExceptions and have something to do with the skin virtual path.

Thanks!

Which skin folder?

I only have one portal.  There is no skin folder in Portals\0.  There is a Skins folder in Portals\_default, but I assume those are the "default skins" you referred to.

Well, I only had a Skin folder in Portal\_default.  I assume that when DNN "defaults back" that it is actually using the Skins in _default.

Renaming that folder led to nothing except "An error occurred" when accessing the main page.  Stopping/Restarting IIS did not help.

I finally reverted my DNN back to 4.3.5 and started the upgrade process over again.  Unfortunately, I did not have a backup of the database.  But the main problem this caused was that "Module Definitions" thought a particular version of a module was installed but the source files no longer matched that version.  Updating the affected modules seems to have cleared everything up.

Thanks for the suggestions.