Thanks for your suggestions.

No, I have only a handful of Session variables that I'm using.  And I only lose session some of the time when this happens.

I have a number of pages where this error happens.  The only common thing among them is that this occurs when there are a large number of rows.  The identical grid works fine when I populate the query with "SELECT TOP 1000" …. but when I don't limit the SELECT and it selects 15,000 rows, the grid loads ok, but I get this error when I click on paging (showing 100 records per page).  It's as if it is trying to retrieve the data from say Page 45, but after 15 seconds or so it stops and gives that error.

This is hosted on a large corporate shared server environment, but I am also able to reproduce it on my localhost.  No errors being reported in any of the Application or other logs.  It happens in DEV, TEST, and PROD which are all on different servers.

Rado:

Thanks for your suggestion.  I tried implementing as you suggested, but I'm still getting the "Server does not respond." error popup.

One question I didn't see answered in any of the posts about this was WHERE this should be implemented.

This method worked for me, but I'm not sure it is the correct place to implement.  I have a Master Page, and inside one of the ContentPlaceHolders I added the following to some existing JavaScript code …

 <asp:Content ID="Content1" ContentPlaceHolderID="head" runat="server">
<script type="text/javascript">

        function pageLoad() {
            $find("<%= WebDataGrid1.ClientID%>")._callbackManager.setTimeout(60000);
        }

</script>
</asp:Content>

It runs without error (it finds the object … and I also added an alert to make sure it was firing) … but I'm still seeing the error.

Any other suggestions?

My Build number is:
Infragistics35.Web.v10.3, Version=10.3.20103.1013
(I'm on a corporate server that has 3.5 framework … so can't run 4.0)

This is my WebDataGrid markup in my .ASPX page.
However, I dynamically add columns to the grid (see below)

<ig:WebDataGrid ID="wdgMain" runat="server" Height="92%" 
StyleSetName="Office2007Black" Width="95%" DefaultColumnWidth="100px"
AutoGenerateColumns="False">
  <Behaviors>
    <ig:Activation Enabled="true" />
    <ig:Paging PageSize="25" PagerAppearance="Both">
    </ig:Paging>
    <ig:Selection Enabled="False">
    </ig:Selection>
    <ig:RowSelectors HeaderRowSelectorCssClass="rowSelectorWidth">
    </ig:RowSelectors>
    <ig:ColumnMoving DragMarkupCssClass="">
    </ig:ColumnMoving>
    <ig:ColumnResizing>
    </ig:ColumnResizing>
    <ig:Sorting SortingMode="Single" Enabled="true">
    </ig:Sorting>
    <ig:ColumnFixing>
    </ig:ColumnFixing>
  </Behaviors>
</ig:WebDataGrid>

In the Page_Load event, I loop through a DataReader that contains a list of columns that the user wants to display in the data grid.  A typical iteration to add a column looks like this:

Dim BoundDataField As New BoundDataField
BoundDataField.Key = Trim(dbReaderView("Column_Name") & "")
BoundDataField.DataFieldName = Trim(dbReaderView("Column_Name") & "")
BoundDataField.Header.Text = Trim(dbReaderView("Column_Label") & "")
BoundDataField.Width = CInt(strPixel_Width)
BoundDataField.CssClass = strCellCSS
wdgMain.Columns.Add(BoundDataField)

I also control the pagesize:
wdgMain.Behaviors.Paging.PageSize = CInt(ddlItemsPerPage.Text)

I control how many rows I'm returning based on a dropdownlist.  This results in queries such as:
SELECT TOP 500 ….  SELECT TOP 1000 …. SELECT TOP 5000, or just SELECT which returns all records.

Here are the error scenarios I am experiencing:

With query… "SELECT TOP 500"  with 92 columns in the SELECT statement
(1) WebDataGrid renders fine the first time with paging set to 100 rows per page (takes maybe 30 seconds to load)
(2) click on paging hyperlink
(3) Ajax loading indicator spins for about 10 seconds
(4) Popup error:  Message from webpage … Server does not respond.  OR
    Popup error:  Message from webpage … Deserialization failure: Invalid response.

When using WebExporterExcel on same data grid:

(1) Several minutes of processing
(2) Finally get Save/Open Excel dialog.  Select Open
(3) ERROR:  The connection with the server was reset

Get similar result when I don't limit the number of rows … so for 10 columns and 55,000 rows