Hello, I have this scenario. The WHDG has a dataset as a datasource which is refilled by the DB at each postback. The control is Ajaxenabled and is not inside an update panel. Viewstate for Ajax and data are set to false. The WHDG purpose in the screen is to perform CRUD operations handling the control's events. Right now my problem is that I get the error "Server does not respond" in any action that requires an ajax postback to the server. That is: update, add, delete, etc. However, this is not hte case when I work locally or when the network traffic at the intranet server is fast; that is, after 17:00. So, it seems that there is some time out triggering somewhere. I have tried to set the timeout for the control as big as possible by using: grid._callbackManager.setTimeout(600000); but, I still receive the message after 20 secs. It does not even show the ajax spinning indicator at some times.
Any idea why this is happening and how effectively prevent the control to stop the postback process?
Thanks
Hi jwquiroz,
Thank you for posting in the community.
I tried to implement this scenario by making a callback to the server and forcing the thread to sleep for 20 seconds. In order to make it work, I had to set the timeout of the hierarchical grid's gridView which uses a separate callbackManager. I would suggest that you handle the client-side Initialize event and use something similar to:
ig_controls.WebHierarchicalDataGrid1.get_gridView()._callbackManager.setTimeout(60000);
Please let me know if this helps.
Best Regards,
Petar IvanovDeveloper Support EngineerInfragistics, Inc.http://es.infragistics.com/support
Ok, it seems I talked too fast on this issue. The problem still persists but with a variant. The setTimeout effectively delays the postback time of the control BUT it only does it at the first attempt. That is, after the first successful postback to the server, the control loses its Timeout settings and returns to the previous 20 sec limit. I am handling page onload event and WHDG client event grid initialize. Both events are triggered at the first page load but none of them fires when the control triggers its postback, queries the db, rebinds, etc. So, any ideas on how can persist this timeout setting within postback trips?
THanks!
Ok, that did it. Now the loading goes past the 20 secs. limit without triggering "Server does not respond". The fact that the control can set 2 callbackManager is confusing. Anyway, thanks.