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

HomeHomeOur CommunityOur CommunityGeneral Discuss...General Discuss...Error after upgrading to DNN 5.0.0 - Failed to load view_stateError after upgrading to DNN 5.0.0 - Failed to load view_state
Previous
 
Next
New Post
1/31/2009 6:32 AM
 

 Hi,

last week we upgraded from DNN 4.9 (?) to DNN 5.0.0 on an SQL Server V9 platform. Since then some of the portals (not all) throw the following error after entering the User ID + password to login.

 Some Portals work ok, some throw adifferent error: "Invalid JSON primitive"

 Also, some of the controls and menu items seem to have dropped off some partals.

 Any suggestion would be appreciated.

 Regards, Peter

Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

Exception Details: System.Web.HttpException: 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.

Source Error:

The source code that generated this unhandled exception can only be shown when compiled in debug mode. To enable this, please follow one of the below steps, then request the URL:

1. Add a "Debug=true" directive at the top of the file that generated the error. Example:

  <%@ Page Language="C#" Debug="true" %>

or:

2) Add the following section to the configuration file of your application:

<configuration>
   <system.web>
       <compilation debug="true"/>
   </system.web>
</configuration>

Note that this second technique will cause all files within a given application to be compiled in debug mode. The first technique will cause only that particular file to be compiled in debug mode.

Important: Running applications in debug mode does incur a memory/performance overhead. You should make sure that an application has debugging disabled before deploying into production scenario.

Stack Trace:

[HttpException (0x80004005): 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.]
   System.Web.UI.Control.Loadview_stateRecursive(Object savedState) +306
   System.Web.UI.Control.LoadChildview_stateByIndex(ArrayList childState) +134
   System.Web.UI.Control.Loadview_stateRecursive(Object savedState) +221
   System.Web.UI.Control.LoadChildview_stateByIndex(ArrayList childState) +134
   System.Web.UI.Control.Loadview_stateRecursive(Object savedState) +221
   System.Web.UI.Control.LoadChildview_stateByIndex(ArrayList childState) +134
   System.Web.UI.Control.Loadview_stateRecursive(Object savedState) +221
   System.Web.UI.Control.LoadChildview_stateByIndex(ArrayList childState) +134
   System.Web.UI.Control.Loadview_stateRecursive(Object savedState) +221
   System.Web.UI.Control.LoadChildview_stateByIndex(ArrayList childState) +134
   System.Web.UI.Control.Loadview_stateRecursive(Object savedState) +221
   System.Web.UI.Page.LoadAllState() +312
   System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +1661

[PageLoadException: 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.]
   DotNetNuke.Services.Exceptions.Exceptions.ProcessPageLoadException(Exception exc, String URL) +277
   DotNetNuke.Framework.PageBase.OnError(EventArgs e) +330
   System.Web.UI.Page.HandleError(Exception e) +84
   System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +6776
   System.Web.UI.Page.ProcessRequest(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +242
   System.Web.UI.Page.ProcessRequest() +80
   System.Web.UI.Page.ProcessRequestWithNoAssert(HttpContext context) +21
   System.Web.UI.Page.ProcessRequest(HttpContext context) +49
   ASP.default_aspx.ProcessRequest(HttpContext context) +4
   System.Web.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() +181
   System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) +75

Server Error in '/' Application.

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.

 


Version Information: Microsoft .NET Framework Version:2.0.50727.3082; ASP.NET Version:2.0.50727.3082

 
New Post
1/31/2009 1:28 PM
Accepted Answer 

Delete your browser cookies and cache, and make sure MS AJAX is installed on the server. Thanks...



Alex Shirley


 
New Post
2/3/2009 2:53 AM
 

Hi,

Got it working, but not entirely sure why :-(

1) Copy the new version on top again, make sure all files copy ok.

2) I had problems that related to file permissions in the DNN folder. I reser the permissions so that the NT User Acount used by IIS had the appropriate permissions and my problems disappeared after a reboot.

Not sure what happened, but I suspect the initial DNN install set up permissions, but some new files delivered as part of the upgrade didn't inherit the correct (read) permissions. Anyway, after this it all worked ok.

After checking the permissions I also changed the skins back and forth in an attempt to force a cache update.

3) Clear out you local browser cache.

Hope this assists.

Peter

 

 

 

 
Previous
 
Next
HomeHomeOur CommunityOur CommunityGeneral Discuss...General Discuss...Error after upgrading to DNN 5.0.0 - Failed to load view_stateError after upgrading to DNN 5.0.0 - Failed to load view_state


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