Hi,
I am using Telerik Reporting Q2 2009, and a bug was discovered with the date parameters. I have two of them: Start Date and End Date, both allow nulls.
To recreate the issue, I uncheck the Null checkbox on one, click the "Go to the next month" link a few times, uncheck the Null checkbox on the other, click the "Go to the next month" link once, and I receive a System Error. Note that I did not select a date from the first date selection. With the calendar still open, I clicked the Null checkbox on the next date selection.
This is most reliably recreated in Safari 3
Server Error in '/' Application.
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:
Stack Trace:
Version Information: Microsoft .NET Framework Version:2.0.50727.3082; ASP.NET Version:2.0.50727.3082
I am using Telerik Reporting Q2 2009, and a bug was discovered with the date parameters. I have two of them: Start Date and End Date, both allow nulls.
To recreate the issue, I uncheck the Null checkbox on one, click the "Go to the next month" link a few times, uncheck the Null checkbox on the other, click the "Go to the next month" link once, and I receive a System Error. Note that I did not select a date from the first date selection. With the calendar still open, I clicked the Null checkbox on the next date selection.
This is most reliably recreated in Safari 3
Server Error in '/' 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) +8623897 System.Web.UI.Control.ValidateEvent(String uniqueID, String eventArgument) +72 System.Web.UI.WebControls.Calendar.RaisePostBackEvent(String eventArgument) +51 System.Web.UI.WebControls.Calendar.System.Web.UI.IPostBackEventHandler.RaisePostBackEvent(String eventArgument) +10 System.Web.UI.Page.RaisePostBackEvent(IPostBackEventHandler sourceControl, String eventArgument) +13 System.Web.UI.Page.RaisePostBackEvent(NameValueCollection postData) +175 System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +1565 |
Version Information: Microsoft .NET Framework Version:2.0.50727.3082; ASP.NET Version:2.0.50727.3082
1 Answer, 1 is accepted
0
Hello Jeremy,
We have tried to reproduce this on browsers other than Safari with no luck. On Safari 4 we've managed to encounter it after quick clicking on the calendar dates and clicking preview while Safari still shows loading at the address area.
The calendar control used in the report parameters' area is the standard MS asp:calendar control, so the same issue can be replicated in a simpler scenario where the chosen date is filled in an input value and on a button click this value is increased/decreased by a day. So it would seem like a Safari issue when clicking a bit too fast.
If you can provide us with a sample project and step by step instructions on how to replicate this reliably on other browsers, we would gladly review it and take the time to address such an issue.
All the best,
Steve
the Telerik team
Instantly find answers to your questions on the new Telerik Support Portal.
Check out the tips for optimizing your support resource searches.
We have tried to reproduce this on browsers other than Safari with no luck. On Safari 4 we've managed to encounter it after quick clicking on the calendar dates and clicking preview while Safari still shows loading at the address area.
The calendar control used in the report parameters' area is the standard MS asp:calendar control, so the same issue can be replicated in a simpler scenario where the chosen date is filled in an input value and on a button click this value is increased/decreased by a day. So it would seem like a Safari issue when clicking a bit too fast.
If you can provide us with a sample project and step by step instructions on how to replicate this reliably on other browsers, we would gladly review it and take the time to address such an issue.
All the best,
Steve
the Telerik team
Instantly find answers to your questions on the new Telerik Support Portal.
Check out the tips for optimizing your support resource searches.