Take the 2-minute tour ×
Server Fault is a question and answer site for professional system and network administrators. It's 100% free, no registration required.

I have an issue where my server doesn't serve up pages on the initial request. I have to F5 (refresh) the page serveral times before the page actually gets served. This issue is on the server itself (not network related) because if I browse to the sites by their IP from the server, I'm seeing the same problem. There's nothing in the event logs that looks abnormal. I've tried iisreset and rebooted the maching, still seeing the same issue. This server has been online and serving pages for over a year now and this just started yesterday.

I'm really not sure where to start digging to resolve this? I also did a windows update yesterday, a virus scan and disk defrag, nothing resolved it.

any suggestions would be greatly appreciated.

share|improve this question

2 Answers 2

You should start by putting up a basic HTML and ASP(x) page to see if it's an IIS issue, or something application specific. If the HTML/ASP pages work fine, then troubleshoot your specific application. Otherwise, browse the site from the server itself to rule out network issues. If that still doesn't work, maybe check DNS or other programs running on the system.

share|improve this answer
    
as I said in my OP, I've already tried browsing to the sites themselves from the server directly and am seeing the same behavior. It doesn't matter if it's an html page or an aspx page, I'm seeing the same thing. Sometimes they load right up, others I have to refresh the page 2-10 times before it will load. –  Charles Oct 26 '12 at 18:29
    
In that case i would test via telnet to see where the delay is happening. You can also disable extra ISAPI modules to rule out them interfering. I've seen this kind of stuff happen before when servers are configured with improper dns settings, causing slow reverse lookups on the client IPs. –  localhost Oct 26 '12 at 18:42

I would enable failed request tracing.

  • Open IIS Manager
  • Select a site and enable "Failed request tracing" from the actions on the right.
  • Then in the IIS section of the site, open 'Failed Request Tracing rules'
  • Add a new rule for 'All content', Status code: 200, all providers.
  • Hit the site in a browser,
  • Open C:\inetpub\logs\FailedReqLogFiles\W3SVCx\ where x is the id of the site
  • Open the latest *.xml file in a browser, IE on a server usually doesn't work. I would copy the file and the freb.xsl to a workstation and open it there.
  • Under 'Request details' you may be able to see what took so long.
share|improve this answer
    
I'll give this a shot and report back. Thanks. –  Charles Oct 26 '12 at 19:37
    
Of course as soon as I set this up, I'm not seeing loading issues. I'll keep it up though and keep pressing it and report back when I have something. –  Charles Oct 26 '12 at 19:47
    
ok got it fail and have an xml log...what am I looking for in here? I don't have a request details section... –  Charles Oct 26 '12 at 19:51
    
You should not look at the raw XML. View the file in a browser where the xsl has transformed the XML into nice Html. On Windows 7 a double-click on the xml file should open IE. If not, start IE and open the xml file manually. –  Peter Hahndorf Oct 27 '12 at 4:21
    
well the server just miraculously started working normally again this morning. I marked your answer as the answer though because I think this would have lead me down the right path and I will keep it in my back pocket in case it happens again. Thanks for the suggestion. –  Charles Oct 27 '12 at 16:29

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.