Products

Solutions

Resources

Partners

Community

Blog

About

QA

Ideas Test

New Community Website

Ordinarily, you'd be at the right spot, but we've recently launched a brand new community website... For the community, by the community.

Yay... Take Me to the Community!

Welcome to the DNN Community Forums, your preferred source of online community support for all things related to DNN.
In order to participate you must be a registered DNNizen

HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...Portal Aliases unavailable after upgrade to 5.0.0Portal Aliases unavailable after upgrade to 5.0.0
Previous
 
Next
New Post
2/20/2009 6:03 PM
 

After upgrading from version 4.9.1 to version 5.0.0 I clicked the Update Site to Current Framework in the DotNet framework setting (which stated 2.0.50727.1378, (3.0), (3.5))  I'm not sure which process caused the errors I'm now getting or how to proceed.  Any help would be greatly appreciated.

When checking the upgrade log I get:

A critical error has occurred.
Failed to load view_state. The control tree into which view_state is being loaded must match the control tree that was used to save view_state during the previous request. For example, when adding controls dynamically, the controls added during a post-back must match the type and position of the controls added during the initial request.

In site settings under Portal Aliases I see:

Error: Portal Aliases is currently unavailable.
DotNetNuke.Services.Exceptions.ModuleLoadException: The file '/DesktopModules/Admin/PortalAliases/PortalAlias.ascx' does not exist. ---> System.Web.HttpException: The file '/DesktopModules/Admin/PortalAliases/PortalAlias.ascx' does not exist. at System.Web.UI.Util.CheckVirtualFileExists(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.ControlUtilites.LoadControl[T](TemplateControl containerControl, String ControlSrc) at DotNetNuke.UI.Modules.ModuleHost.LoadModuleControl() --- End of inner exception stack trace ---

Andy

 
New Post
2/20/2009 7:16 PM
Accepted Answer 

the 2nd message (missing portalalias) is a known problem that's been resolved for 5.0.1 (due out Monday)

Cathal


Buy the new Professional DNN7: Open Source .NET CMS Platform book Amazon US
 
New Post
3/19/2009 6:42 AM
 

I still get the Portal Alias problem after upgrading to DNN 5.0.1

 
Previous
 
Next
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...Portal Aliases unavailable after upgrade to 5.0.0Portal Aliases unavailable after upgrade to 5.0.0


These Forums are dedicated to discussion of DNN Platform and Evoq Solutions.

For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

  1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
  2. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
  3. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  4. No Flaming or Trolling.
  5. No Profanity, Racism, or Prejudice.
  6. Site Moderators have the final word on approving / removing a thread or post or comment.
  7. English language posting only, please.
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out