Invalid postback or callback argument, occurred during Update membership events
Last Updated December 07, 2007
During an Update membership (Altiris Notification Server Error1.jpg) an error occured:
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.
Viewstate represents the state of the page when it was last processed on the server. The contents of the page are stored in a container and moved to and from the server on each request. By default, ASP.NET validates the contents of viewstate to ensure that it has not been tampered. If this validation test fails, an invalid viewstate exception is thrown. Some known issues that cause this test to fail are listed below.
Application Pool Recycling
IIS 6 will periodically recycle the application pool to maintain the health of the application pool. At the instance when the application pool is being recycled, browser requests may sometimes result in an invalid viewstate error. The fix in this case is to adjust the settings on the application pools so that recycling is less likely to occur at peak periods. This issue represents a bug since the application pool is supposed to gracefully handle this condition.
Change the DefaultAppPool > Properties > Recycling to 1740 minutes, as the default should be, and disable the Recycling for a number of requests.
Applies To Notification Server 6.0 SP3 Microsoft .NET Framework* 1.1.4322.2300 ASP.NET* 1.1.4322.2300
Imported Document ID: TECH35752
Subscribing will provide email updates when this Article is updated. Login is required to Subscribe