locked
Internet Explorer loses connection to ASP.NET website RRS feed

  • Question

  • User1239704775 posted

    Hi everybody,

    I'm messing around with a nasty and quite unspecific problem: We are driving an ASP.NET / AJAX application built on ASP.NET 2.0 and ASP.NET AJAX 1.0 on a Windows Server 2003 / IIS 6 machine. The application is a project management system, running only in the local intranet.

    For some users the following phenomenon occures: If they try to load a certain site  with the Internet Explorer (6.0, 7.0 - doesn't matter) the site starts loading (you can see the caption in the title bar) and a short time later the loading process stops with an message like "Unable to load the site http://server/site - conection was lost" in a popup message box. Unfortunately I only can give you the German text - it is "Die Seite http://server/site konnte nicht geladen werden - die Verbindung wurde abgebrochen." Other users do never run into this trouble (at least until now).

    The site on which the problem occurs consists of some JavaScript, a database-bound DataGrid and some AJAX stuff (UpdatePanels, WebService - bound DropDown boxes etc.). Neither the Event Log on the webserver nor the IIS logfiles shed light on what is going wrong here. The last thing the log file shows is a POST to the mentiond site, the response code is 200 (OK). The problem does not occure when Firefox is used as browser. The site is configured by the IIS for non-anonymous access and integrated windows authentication. The ASP.NET application uses impersonation with a user well-equiped with rights. All relevant user groups have appropriate rights set on the applications folders (what shouldn't matter because only the ASP.NET user accesses these ones...).

    I installed Fiddler 2.0 on the users client to take a look at the HTTP traffic. So I saw that the content of the response to the last post is only one byte long and the respsonse contains only one small letter "s".

    I'm running out ouf ideas a) how to find any helpful information about the problem (logfiles etc.) and b) about the reason for that. We don't use any specific HTTP modules (besides the ones used by the AJAX framework). The problem does only occure on one specific site - which is stupidly the main entry point. Other sites in the application are built by a similar schema (AJAX, data-bound tables) and do NOT cause the problem. One difference may be that the faulty site is quite large because of many data shown in the table.

     

    Could anyone provide some helpful hint to me or has a similar problem?

     

    Desperately regards,

    ReneMT 

    Tuesday, March 6, 2007 12:17 PM

All replies

  • User1073881637 posted

    Good description.  Hmm...The only IIS related things I can suggest to check is how big the requests are coming into web server. If the site is mainly using a web service to retrieve data, then I suspect the problem would be more on the database side than anything.  You might want to try increasing the request timeout either in IIS or asp.net.

    http://msdn.microsoft.com/en-us/library/ms998562.aspx#scalenetchapt10_topic14

    I would try running sql profiler to see if you can spot any long running queries. http://msdn.microsoft.com/en-us/library/ms979207.aspx  I would also check http://forums.asp.net AJAX forums.  They might have some specific AJAX tips not related to IIS.  WFETCH is similar to fiddler, this might help find some other HTTP related issues.  Hope that helps.

    Friday, March 9, 2007 2:41 AM