Portal Engine Questions on portal engine and web parts.
Version 7.x > Portal Engine > Failed to load viewstate - Custom Filter web part View modes: 
User avatar
Member
Member
kashank - 9/9/2013 11:06:33 AM
   
Failed to load viewstate - Custom Filter web part
I had a fully functional custom filter web part built. I used the example in the developer guide under Development > Web parts > Data source web parts: Developing custom filters

Over the weekend, I installed a hotfix and am now at v7.0.49.

Now the custom filter is not functioning properly, and I cannot check out the page that utilizes the filter. Anytime I attempt to check out the page, I get the following error:

here was an error processing the page. The error can be caused by the configuration of some component on the master page. Check the master page configuration or see event log for more details. Original message: Failed to load viewstate. The control tree into which viewstate is being loaded must match the control tree that was used to save viewstate 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.

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.Exception: There was an error processing the page. The error can be caused by the configuration of some component on the master page. Check the master page configuration or see event log for more details. Original message: Failed to load viewstate. The control tree into which viewstate is being loaded must match the control tree that was used to save viewstate 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:

An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.

Stack Trace:


[Exception: There was an error processing the page. The error can be caused by the configuration of some component on the master page. Check the master page configuration or see event log for more details. Original message: Failed to load viewstate. The control tree into which viewstate is being loaded must match the control tree that was used to save viewstate 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.]
CMS.UIControls.PortalPage.OnError(EventArgs e) +408
System.Web.UI.Page.HandleError(Exception e) +164
System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +12573451
System.Web.UI.Page.ProcessRequest(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +12572973
System.Web.UI.Page.ProcessRequest() +119
System.Web.UI.Page.ProcessRequest(HttpContext context) +99
System.Web.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() +913
System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) +165

Does anyone have any ideas as to where the problem is?

User avatar
Member
Member
kashank - 9/9/2013 1:43:13 PM
   
RE:Failed to load viewstate - Custom Filter web part
Randomly, this issue seems to have taken care of itself, I no longer get this error message and can check in/out the files in question with no issue.

I'm not sure what exactly fixed the issue, but I restarted the web app and cleared the cache somewhere around the time it started working.

User avatar
Kentico Legend
Kentico Legend
Brenden Kehren - 9/10/2013 10:07:03 AM
   
RE:Failed to load viewstate - Custom Filter web part
Kentico uses cache heavily. If you can't clear things up by clearing the cache in your browser, navigate to CMSSiteManager>Dashboard and clear the cache and/or restart the application there.