I've just installed a fresh copy of Windows Server 2008 x64 with IIS7 and PHP (fast CGI). However, I'm noticing that after moving my web site from a similarly specified machine to this one, I'm getting issues.

The issue seems to be that randomly, as I'm clicking through the web pages being served, the browser will suddenly hang saying "waiting for mysite.com...".

Sometimes the page will then timeout, or finally resolve after 20 to 30 seconds, but maybe missing the CSS style sheet.

Very strange, as this is the only website installed on this new server, and only myself using/testing it. Server is installed in the same data centre below the old server.

Has anyone else had a similar problem? I tried increasing the max workers pool to 10 (from 1), but this has no effect. Seems to happen most frequently after 1 or 2 minutes of inactivity on the website, then trying to load/refresh a web page.

Many thank for any info and help.

Kind Regards, Seb


With a lot of things in play here I would start by troubleshooting at the lowest level. As they say in IT crowd have you tried turning it off and on again :) Sometimes i find a simple iisreset can fix it.

If it is more complex than that, as it sounds, then start by working backwards to identify where the problem actually is.

Start by disabling php altogether, put some regular html pages up and see if those load fine. If they do then it sounds like it is a php issue. Considering things like style sheets not loading it sounds definitely more like an IIS issue though. First make sure to enable logging on the iis service if it isnt already (is by default) http://technet.microsoft.com/en-us/library/cc754631%28WS.10%29.aspx.

Start looking through the IIS logs and the windows event viewer to see if anything is out of the ordinary.

If everything looks fine you should doubly confirm the following:

Make sure it's not a network issue. While both boxes are in the same datacenter it could be there is a duplex mismatch or some errors on the port the server is plugged in to. Do an FTP transfer, or some other transfers to and from the machine and see if you experience the same issues with http. Try and browse from the server itself or from the same LAN. Obviously not great to install web browsing software on a server so make sure to remove it afterwards or re-secure IE.

Run a hardware check. If this is a managed service ask your provider to do a hardware check on the machine. Most common boxes have a bootable cd you can run to check the hardware.

Check the utilization of the server. When browsing the site is there any sudden spike in memory or cpu that looks unordinary?

Try a different web server. While I wouldnt recommend installing apache on windows, it would be a good way to narrow it down between an IIS problem and a server problem. If you see the same issues with apache, then its likely your machine. If you don't then sounds like it is an IIS problem.

Hope this helps.


After going through pablo's list: test your web application locally to the server (without going through a proxy). This will, at least, remove routing and potential proxy issues from the list. (Some older bluecoat proxies cause application failures with IIS https extensions for example).

Ensure that your application timeout is set to a fair interval and that you have no CPU limits set that may be causing issues in the advanced settings of the application pool. Also make sure that you have a fiar queue length.


Check you are not running out of memory for your IIS app pool

  • You may want to give a brief explanation on how you'd do this. – TheFiddlerWins Apr 13 '18 at 15:14

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

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