Good day.
i have a webCombo placed on an ASP.NET page. when the page is first rendered, it is bound fine. i can select the items as desired. however, upon a postback, i receive the following error:
Index was outside the bounds of the array.
[IndexOutofRangeException: Idex was outside the bounds of the array.]
Infragistics.WebUI.WebCombo.WebCombo.LoadPostData(string postDataKey, NameValueCollection values) + 1243
system.Web.UI.Page.ProcessPostData(NameValueCollection postData, Boolean fBeforeLoad) + 549
system.web.ui.page.processReqeustMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) + 2198
Version Info: MS .NET, Version 2.0.50727.1433; ASP.NET Version:2.0.50727.1433
any help would be appreciated.
thanks.
Kevin,
Thanks for your message. We do not currently have enough information on the cause of this specific error message to be able to determine what its cause was.
The fact that you're using Linux may be part of the specific issue you're encountering, since Linux is not an environment that Infragistics has tested (etiher as a server machine or a client machine), and so is not supported by Infragistics. You can view further details on the environments we support on the Supported Environments page of our website.
If you can reproduce this using an operating system that we support, please submit a support request to provide additional details - preferably including a sample project that we can run and debug that reproduces the issue. This issue is likely to take in-depth research to resolve, and this is best done by a Developer Support Engineer dedicated to researching your issue.
Hi Vince,
I wonder if there is any solution or work-around for this issue. I experienced the same issue. This issue only occur in Linux or in Prizm. It is difficult to trace and debug. It occurs on the postback at the the it is reconstructed.
Thanks,
Kevin
I don't believe we have enough information to determine what's going on here.
What version of the toolset are you using? If you're using an older version of the toolset, this may be a bug that was fixed, so you may want to test this in a more recent version or with a hot fix.
Otherwise, I suggest that you submit a support request and attach a sample that we can run and debug that reproduces this behavior. A Developer Support Engineer can then research using this sample and determine what possible courses of action are available.