+1-888-365-2779
Try Now
More in this section

Forums / Bugs & Issues / Error in moving in a news item from view-edit-history

Error in moving in a news item from view-edit-history

5 posts, 0 answered
  1. Vangelis
    Vangelis avatar
    153 posts
    Registered:
    07 Jan 2006
    27 May 2007
    Link to this post
    I went on news module and I was moving from view -edit - history to check saved time. I then just moved from one tab to another it suddenly appeared the following errors.

    Server Error in '/ist.eu' Application.

    Invalid postback or callback argument.  Event validation is enabled using <pages enableEventValidation="true"/> in configuration or <%@ Page EnableEventValidation="true" %> in a page.  For security purposes, this feature verifies that arguments to postback or callback events originate from the server control that originally rendered them.  If the data is valid and expected, use the ClientScriptManager.RegisterForEventValidation method in order to register the postback or callback data for validation.

    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.ArgumentException: Invalid postback or callback argument.  Event validation is enabled using <pages enableEventValidation="true"/> in configuration or <%@ Page EnableEventValidation="true" %> in a page.  For security purposes, this feature verifies that arguments to postback or callback events originate from the server control that originally rendered them.  If the data is valid and expected, use the ClientScriptManager.RegisterForEventValidation method in order to register the postback or callback data for validation.

    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:

    [ArgumentException: Invalid postback or callback argument.  Event validation is enabled using <pages enableEventValidation="true"/> in configuration or <%@ Page EnableEventValidation="true" %> in a page.  For security purposes, this feature verifies that arguments to postback or callback events originate from the server control that originally rendered them.  If the data is valid and expected, use the ClientScriptManager.RegisterForEventValidation method in order to register the postback or callback data for validation.]
    System.Web.UI.ClientScriptManager.ValidateEvent(String uniqueId, String argument) +2082553
    System.Web.UI.Control.ValidateEvent(String uniqueID, String eventArgument) +106
    System.Web.UI.WebControls.TextBox.LoadPostData(String postDataKey, NameValueCollection postCollection) +31
    System.Web.UI.WebControls.TextBox.System.Web.UI.IPostBackDataHandler.LoadPostData(String postDataKey, NameValueCollection postCollection) +11
    System.Web.UI.Page.ProcessPostData(NameValueCollection postData, Boolean fBeforeLoad) +408
    System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +4526


    Version Information: Microsoft .NET Framework Version:2.0.50727.42; ASP.NET Version:2.0.50727.210



    Server Error in '/ist.eu' Application.

    Validation of viewstate MAC failed. If this application is hosted by a Web Farm or cluster, ensure that <machineKey> configuration specifies the same validationKey and validation algorithm. AutoGenerate cannot be used in a cluster.

    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: Validation of viewstate MAC failed. If this application is hosted by a Web Farm or cluster, ensure that <machineKey> configuration specifies the same validationKey and validation algorithm. AutoGenerate cannot be used in a cluster.

    Source Error:

    [No relevant source lines]

    Source File: c:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\Temporary ASP.NET Files\ist.eu\16962f92\6c24bcb3\App_Web_h1uoag9w.6.cs    Line: 0

    Stack Trace:

    [HttpException (0x80004005): Unable to validate data.]
    System.Web.Configuration.MachineKeySection.GetDecodedData(Byte[] buf, Byte[] modifier, Int32 start, Int32 length, Int32& dataLength) +2549708
    System.Web.UI.ObjectStateFormatter.Deserialize(String inputString) +214

    [ViewStateException: Invalid viewstate.
    Client IP: 127.0.0.1
    Port: 2996
    User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.3) Gecko/20070309 Firefox/2.0.0.3
    ViewState: Pd9c3B7JA2x534ZUvvG0GcdmLWvk3goYvmmZAWIud4teCVms14hNJaQ+98UciCYhzYZwzVugw6vVEIRbDNpXiF5O8L2aU5sixgPSRiHu2XZaIoX6U/YgOIHQ/TErUV2/pqkw+SfQXJCTe7xV+MY4K3BpwqsH7KBfEpHVaeH7s4+ScgZ/nITZzP+2XQN7TK00dcTwlFuHNd+Q4V2yYz8wc8zWWDPzD4B+YAn0qYe2YweF3+hHQUOjz38CAqbQLmmbXxxf0s1pDhqUt1XkLmmAthh0YJ0MZlAOWRGE940bL8Olpr6RtbewWhC+MmFSfY5Oms3oI5Vy2RgJcP4DP3lSb+Y1W/FXmxc1zsjj7nZHfZwraLFt9oUjxR7DMrag4NPSOBFvJAVpx22fEgITaOCghbQxBRRDW9bLb03kAOU4y6bOrmf/Oh3q+xVYLYFGGwzf7ElgHpj4Ia0nh1O/f9/ufy5ONHxCyISo2WTGRs9vS0oM5uMfCFl3tx6gMuue41CE9m+cdZr3y/SHi3H1dfUdMYrZVEMPpI/Z8PtST+pWmT+T0GsFCa23xO7GBiNV8BNJYmiyWI4hhQIeqRrI/WidpkNt3UD+13RNn6owXWJV4FrPq7LptZ3bfR9jibrKYrnif2cpPtMcJqWvvjxTS/+z9PgpplAd/9DQBjcYILLZ2bwYdHtcPx2cXhuwQivXc5pXdtltUkNmH9tUcXf1lc5zvz7cZxCk7qyThhxfpjoN1g/6utgdH4Z/F1FIF/OFk63TB2o51aJJKKpxBQChqUI/SyYRrI6dlLsByhEmez8+YBzFsaDH7a8tmly0jXEg6eY4/0rjRPgJf/H154tqjmp/dEifpTkWTEVXXm...]

    [HttpException (0x80004005): Validation of viewstate MAC failed. If this application is hosted by a Web Farm or cluster, ensure that <machineKey> configuration specifies the same validationKey and validation algorithm. AutoGenerate cannot be used in a cluster.]
    System.Web.UI.ViewStateException.ThrowError(Exception inner, String persistedState, String errorPageMessage, Boolean macValidationError) +116
    System.Web.UI.ObjectStateFormatter.Deserialize(String inputString) +251
    System.Web.UI.ObjectStateFormatter.System.Web.UI.IStateFormatter.Deserialize(String serializedState) +4
    System.Web.UI.Util.DeserializeWithAssert(IStateFormatter formatter, String serializedState) +37
    System.Web.UI.HiddenFieldPageStatePersister.Load() +220
    System.Web.UI.Page.LoadPageStateFromPersistenceMedium() +83
    System.Web.UI.Page.LoadAllState() +35
    System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +6953
    System.Web.UI.Page.ProcessRequest(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +154
    System.Web.UI.Page.ProcessRequest() +86
    System.Web.UI.Page.ProcessRequestWithNoAssert(HttpContext context) +18
    System.Web.UI.Page.ProcessRequest(HttpContext context) +49
    ASP.sitefinity_admin_modules_aspx.ProcessRequest(HttpContext context) in c:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\Temporary ASP.NET Files\ist.eu\16962f92\6c24bcb3\App_Web_h1uoag9w.6.cs:0
    System.Web.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() +154
    System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) +64


    Version Information: Microsoft .NET Framework Version:2.0.50727.42; ASP.NET Version:2.0.50727.210

  2. Sean
    Sean avatar
    271 posts
    Registered:
    31 May 2006
    28 May 2007
    Link to this post
    Hi Vagelis,

    I have this problem too all the time, it basically happens if you cause a postback before the page has fully loaded.  It is really noticeable when using it over a very slow connection.

    This problem has been discussed before .

    Hope that helps
    Sean
  3. Vassil Daskalov
    Vassil Daskalov avatar
    261 posts
    Registered:
    18 May 2013
    28 May 2007
    Link to this post
    Hi Vagelis,

    This error usually occurs if you force postback before waiting for the whole page to load. This is so due to the fact that asp.net event validation is enabled and the corresponding javascript code is located at the end of the page. If attempt for postback is called before the page load, this script is not loaded yet and an error is thrown. In a nutshell, event validation is a technique used by ASP.NET 2.0 to ensure that the data being sent back to the server on postback is an expected value and is designed to help prevent injection attacks.  Fortunately, there is an option to disable the event validation from the <%@ Page /@%> directive by the EnableEventValidation attribute.

    Kind regards,
    Vassil Daskalov
    the Telerik team

    Instantly find answers to your questions at the new Telerik Support Center
  4. Kevin Pipher
    Kevin Pipher avatar
    91 posts
    Registered:
    30 Nov 2005
    16 Aug 2007
    Link to this post
    Hi all,

    What are the implications of turning off validation to work around the exception issue? Will it affect the CMS functionality negatively in any way?

    One workaround I thought of, is to catch the specific exception in the global Application_Error handler of global.asax. It could redirect the user to a friendly error message explaining the issue and telling them to go back and try again.

    The exception is somewhat harmless, but will be very scary to CMS users who aren't developers.

    What are your thoughts on this?

    Kevin.

    p.s. Sorry I also posted this reply in another thread in the retired 3.0 pre-release forum by accident, so there may be a duplicate post.
  5. Vlad
    Vlad avatar
    498 posts
    Registered:
    15 Jul 2016
    17 Aug 2007
    Link to this post
    Hello Kevin,

    "This event validation mechanism eliminates the risk of unauthorized postback requests and callbacks. It instructs ASP.NET to validate only those specific events that can be raised on the control during a postback request or callback. With this model, a control registers its events during rendering and then validates the events during the post-back or callback handling. All event-driven controls in ASP.NET now use this feature by default."

    Turning it off will not affect Sitefinity functionality.

    Thank you for the idea, we will consider it for the future improvements of Sitefinity.

    Kind regards,
    Vlad
    the Telerik team

    Instantly find answers to your questions at the new Telerik Support Center
Register for webinar
5 posts, 0 answered