Thanks. I was planning on updating to 20121.2156_SR already. Glad to know this corrects the known issue. I have already ensured .ClearDataSource() was called before binding a "new" DataSet. That is what I thought was correct, but still noticed the exceptions in the ASP.NET log on the production server. I plan to upgrade to 12.2 in the next quarterly release of my application. Thanks again.

Feedback?

I'm getting the same error on a page with 2 grids. Both are bould to a non-persistent DataSource (SQL DataSet) on button click.

Grid_1 has DataViewState enabled. It is rebound on each button click.

Grid_2 has DataViewState disabled and filtering enabled. The DataSource is saved to a session variable and rebound during Page_Load. If the user clicks the button, and new DataSet is retrieved, set as the DataSource and then saved to the session variable for next postback.

I know I should not call ClearDataSource() during Page_Load as that will clear and selected cells on postback. Should I be calling ClearDataSource() during button click before binding the new DataSet?

// Convergence Waves

DataSet waves = Common.GetDataSetSQL("EXEC [dbo].[GetAppWaves] 'LIST', '" + sSite + "'");

WebDataGridConvergenceWaves.DataSource = waves;

WebDataGridConvergenceWaves.DataBind();

// Vertical/Regional/DPTs

DataSet apps = Common.GetDataSetSQL("EXEC [dbo].[GetDeployableApplications] '" + WebDropDownRegion.SelectedItem.Value + "', '" + Session[HiddenField_SiteOfComputer.Value].ToString() + "'");

WebDataGridApplications.DataSource = apps;

WebDataGridApplications.DataBind();

// Save DataSet to session variable for grid filtering

Common.SaveDataset(apps, HiddenField_WebDataGridApplicationsDataSet.Value);