We are still using WebGrid 6.0. 

This error occurs intermittently in prod environment and whenever it happens, the entire app becomes unusable. All the users get thrown out of app. The entire app can only be recover by doing IIS Reset.

It's very critical for us to resolve it.

As I already stated in this thread, we bind the webgrid using objectdatasource and objectdatasource is bind to a class which in turn execute SP call. Once resultset is been retrieved from the SP, we check if there are any rows in it, if resultset is empty then we explicitly add one row into it as below :

{

if (ds.Tables[0].Rows.Count == 0)

{

DataRow dr = ds.Tables[0].NewRow();

ds.Tables[0].Rows.Add(dr);

}

}

catch { }

Do you think by any chance above code might throw this error ?

If you look at the stacktrace, you could see that once WebGrid.OnLoad is called, all the stack trace contains the method calls related to data binding to webgrid. We do not have much control over those methods.

Is it possible, if anybody from intersoft can have verbal communication with us, so that we can look more closely into it. It would be highly appreciated. By any chance , are you available in US EST time ?

Hi Glenn,

In our app, WebGrid is bound to ObjectDataSource and ObjectDataSource is bound to a class.

This class is having two functions which provides dataset and count of records. It doesnot happen that frequently, but whenever it happens , it brings the entire application down. Then application can be recovered only by restarting IIS. Restart of IIS in production environment is not suggestable.