http://www.intersoftsolutions.com/Community/WebGrid/Unable-to-communicate-with-server---exporting-from-webgrid/http://www.intersoftsolutions.comenCopyright 2002 - 2015 Intersoft Solutions Corp. All rights reserved.60http://www.intersoftsolutions.com/Community/WebGrid/Unable-to-communicate-with-server---exporting-from-webgrid/Tue, 05 Nov 2013 23:02:26 GMTyudiUnable to communicate with server webgrid<p><span style="color: rgb(31, 73, 125);">Thank you for your post suggesting possible solution regarding exporting problem which happen when deploying your project to Amazon virtual server. If you don’t mind, we’d love to hear the result after raising the timeout.</span></p><p><span style="color: rgb(31, 73, 125);">Look forward to hearing back from you.</span></p> <p><span style="color: rgb(31, 73, 125);">Thanks again for your message. Your ideas and suggestions are always welcome.</span></p>http://www.intersoftsolutions.com/Community/WebGrid/Unable-to-communicate-with-server---exporting-from-webgrid/Thu, 31 Oct 2013 18:44:40 GMTlarsknoxUnable to communicate with server webgridI wanted to share a possible solution for anyone encountering this error. Unfortunately, this very general error message could mean many different issues. I'd like to share mine so the next person doesn't have to agonize over this. <div><br /></div> <div>We've been using the webgrid for many years. Recently we've moved our application from physical hardware to Amazon virtual servers and we are using an Elastic Load Balancer.</div> <div><br /></div> <div>The symptom we kept seeing when trying to Export (a LOT of data) from our webgrid was we would wait for 60 seconds and then see the "Unable to communicate with server" error message. Debugging all of the obfuscated Intersoft javascript was a nightmare. We ultimately resorted to using Fiddler2 (highly recommended tool) and discovered the WebGrid was receiving an HTTP/504 error at the end of the 60 seconds. We also determined that the IIS server would still continue to build the export on the backend even after the browser received the HTTP/504. We discovered this after setting e.ReportInfo.CacheToDisk = true and e.ReportInfo.CacheToDiskLocation = 'c:\some\file\location' in the WebGrid_Export method in our ASPX code behind.</div> <div><br /></div> <div>One definition for an HTTP/504 is "<span style="font-family: arial, sans-serif; font-size: 9pt;">A server (not necessarily a Web server) is acting as a gateway or proxy to fulfill the request by the client (e.g. your Web browser) to access the requested URL. This server did not receive a timely response from an upstream server it accessed to deal with your HTTP request."</span></div> <div><span style="font-family: arial, sans-serif; font-size: 9pt;"><br /></span></div> <div>Then we found this forum post which indicates that Amazon Elastic Load Balancers have a 60 second timeout: <a href="https://forums.aws.amazon.com/thread.jspa?messageID=491594#491594" style="font-family: calibri, sans-serif; font-size: 11pt;">https://forums.aws.amazon.com/thread.jspa?messageID=491594#491594</a></div> <div><br /></div> <div>The problem is, there is no way to observe or change the 60 second timeout on the ELB from the AWS console or API. You MUST file a support ticket with Amazon (which might require a support CONTRACT) in order to raise the timeout up to a maximum of 17 minutes.</div> <div><br /></div> <div>Once our support request was completed, another retest and all of our WebGrid exporting began to work beyond the 60 second ELB timeout.</div> <div><br /></div> <div>Hope this helps someone else.</div> <div><br /></div> <div>L</div> <p style="vertical-align: top;"><span lang="undefined" style="font-size: 9pt; font-family: arial, sans-serif;"><o:p /></span></p>