« Previous Next »

• 10-30-2009, 8:47 PM

  avanzis Joined on 05-17-2007, 12:44 PM Posts 4

  The same raquest is randomly served or not Reply Contact We are running an IIS server with several pools. All pools serve all sites requests for hours or days. But suddenly, one app pool starts to behave in a strange manner. Lets say you request a single image (or any other url). Sometimes it's served and other times not. If we make several repeated requests, we usually receive a 200 OK response from 1-8 times, and then 1-2 times with no response... and then more OK responses, 1-2 no reponse...  It's not a 404 or any other response, just no response. The original issue has been happening in an ASP.Net site, but we could later reproduce it in a another "html only" test site on the same pool, so it does not seem an ASP.NET related problem. Note that only one pool every time is affected, the others continue running smoothly. If we simply stop and start the affected pool, it returns to work as usual. We are running a Windows 2003 server, 64 bits, IIS 6 running in 32 bits mode. We have not found anything by the following ways: - Application event log. Nothing found. - HTTPErr logs. Nothing found. - Tracing the iis dump whith logman.  Any ideas about how to find out what's happening??

• 10-30-2009, 9:00 PM

  In reply to

  lextm Joined on 10-22-2008, 12:18 AM Shanghai, PRC Posts 1,396

  Re: The same raquest is randomly served or not Reply Contact You missed one important piece. Why not track down those failed requests from IIS logs for the web site? If a request to the image never arrives on IIS side, there will be no response to browser. If it arrives, there must be a record in IIS logs or HTTP error logs so that you can find its status. Application event logs and IIS dumps are not useful at this moment, as we don't even know what happens to those requests. Lex Li Support Engineer at Microsoft --------------------------- This posting is provided "AS IS" with no warranties, and confers no rights.

• 10-30-2009, 9:13 PM

  In reply to

  avanzis Joined on 05-17-2007, 12:44 PM Posts 4

  Re: The same raquest is randomly served or not Reply Contact Sorry, for not having provide all the information. In the standard IIS W3C log, we have no information about these "failed" requests. The only requests logged are the ones with 200 OK response. About HTTP error logs, we only know about HTTPErr (c:\windows\sytem32\LogFiles\HTTPErr), and we don't find anything interesting for this issue. Should we look in any other place? Thanks for your fast answer! Note 1: We are now making this tests request from "fiddler", in order to avoid any browser effect and having more control and information about requests and responses. Note 2: We discard any client firewall/proxy since it happens connecting from different locations. We also discard firewall issues at server, since the other pools run unaffected.

• 10-30-2009, 9:24 PM

  In reply to

  lextm Joined on 10-22-2008, 12:18 AM Shanghai, PRC Posts 1,396

  Re: The same raquest is randomly served or not Reply Contact If you already dug IIS logs and HTTP error logs and could not find any records for the failed requests, I guess they never arrived on IIS server. This can be confirmed by network traffic capture at the same time on both the IIS server and your test client. Microsoft Network Monitor can serve you well. http://www.microsoft.com/downloads/details.aspx?familyid=983B941D-06CB-4658-B7F6-3088333D062F&displaylang=en Such networking issues are also discussed under our networking forum, http://social.technet.microsoft.com/Forums/en/winserverPN/threads Lex Li Support Engineer at Microsoft --------------------------- This posting is provided "AS IS" with no warranties, and confers no rights.

• 10-30-2009, 9:40 PM

  In reply to

  avanzis Joined on 05-17-2007, 12:44 PM Posts 4

  Re: The same raquest is randomly served or not Reply Contact Thank you for your attention.  Request seems to arrive to the server.  Using network monitor, we can see how one request is arriving to the server, and we don't get any request. We made 4 requests with fiddler. 200 OK, response for the first 3, no response at 4th. That's what network monitor shows: 3 3603.765250  {HTTP:15, TCP:14, IPv4:32} 84.126.XXX.XXX DWS96  HTTP HTTP:Request, GET /images/vxhtml10.gif 4 3606.343375  {HTTP:29, TCP:28, IPv4:32} 84.126.XXX.XXX DWS96  HTTP HTTP:Request, GET /images/vxhtml10.gif 5 3607.905875  {HTTP:42, TCP:34, IPv4:32} 84.126.XXX.XXX DWS96  HTTP HTTP:Request, GET /images/vxhtml10.gif 6 3611.015250  {HTTP:45, TCP:43, IPv4:32} 84.126.XXX.XXX DWS96  HTTP HTTP:Request, GET /images/vxhtml10.gif 7 3612.109000  {HTTP:45, TCP:44, IPv4:32} 84.126.XXX.XXX DWS96  HTTP HTTP:Request, GET /images/vxhtml10.gif

• 10-30-2009, 10:05 PM

  In reply to

  lextm Joined on 10-22-2008, 12:18 AM Shanghai, PRC Posts 1,396

  Re: The same raquest is randomly served or not Reply Contact So you do have Network Monitor logs from both the server and the client? The client side log alone is useless. When you have both, using the successful requests to squeeze out the failed ones from both sides. You can find a network expert to assist or open a support case via http://support.microsoft.com Lex Li Support Engineer at Microsoft --------------------------- This posting is provided "AS IS" with no warranties, and confers no rights.

• 10-31-2009, 6:34 AM

  In reply to

  avanzis Joined on 05-17-2007, 12:44 PM Posts 4	Re: The same raquest is randomly served or not Reply Contact That was network log at server. I did not post the client log. It shows that it's not a networking issue.

• 10-31-2009, 7:35 PM

  In reply to

  lextm Joined on 10-22-2008, 12:18 AM Shanghai, PRC Posts 1,396

  Re: The same raquest is randomly served or not Reply Contact Since the packets arrived at server side, there is no reason that they were not logged in either IIS logs or HTTP error logs. I suggest you open a support case via http://support.microsoft.com so our support team can review all log files for you and help locate the root cause.  Regards, Lex Li Support Engineer at Microsoft --------------------------- This posting is provided "AS IS" with no warranties, and confers no rights.