Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

Everything worked fine a few days ago. I think everything worked perfectly fine till I tried to create an AMI of this EC2 instance. It appears that the creation attempt caused the server to become non-responsive, so I stopped that process and restarted the server. It's Windows Server 2008 R2, running 6 ASP sites and 6 PHP sites. All PHP sites identical, all ASP sites identical.

On some of the sites, they load fast and without incident. Some of them put W3WP to 100% and they just don't load, eventually throwing a 500 error and subsequent refreshes say the site is unavailable. (Sometimes - I just tried again and got no unavailable errors, but still got 500 after the server timed out)

None of this makes sense to me, they should all load the same and they shouldn't have been effected by any of this. Any ideas would be great!

share|improve this question
Have a look at the answers to W3WP.EXE using 100% CPU. – David Schwartz Oct 23 '12 at 19:24
up vote 0 down vote accepted

The problem was that the IIS config reverted and put some PHP sites to ASP, and all ASP sites weren't working. ASP wasn't working because the data it was expecting to loop through from MySQL wasn't there, somehow the SQL config got corrupted as well. So basically my issue was I needed to re-configure SQL so ASP would load, and re-configure IIS to point my php sites to php.

share|improve this answer

Your Answer


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.