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

I have an intranet website running on IIS 7. When I try to load my site, it reacts differently every time. Here are the following different scenarios that occur when I try to load my site:

  1. The site loads right away and is working properly
  2. The site loads slowly and some my styling/images/javascript did not appear to load correctly.
  3. I receive a "503 service unavailable" error

Any ideas why this is happening?

share|improve this question

migrated from Aug 28 '12 at 12:59

This question came from our site for professional and enthusiast programmers.

Sounds like your website might be getting overloaded with traffic. – Andrew Barber Aug 28 '12 at 12:28
how can i check if t@z the case??? – Gayanee Wijayasekara Aug 28 '12 at 12:29
Logs, counters, etc. More of a server admin question, really. – Andrew Barber Aug 28 '12 at 12:30
1) Who is t@z? 2) You don't provide enough details to advise you. 3) It IS mostly admin question, so this is wrong place to ask. – Germann Arlington Aug 28 '12 at 12:31
It's not necessarily your website, it might be anything else that is clogging the server's resources. What you should do is open Task Manager on your server, and see if there's any process using up your CPU or memory. – Svarog Aug 28 '12 at 12:31

So finally my problem was solved. The problem was in the IIS configuration, the maximum number of connections was set to 5. Simply increasing it solved the error.

share|improve this answer

full description of the error:

The Web server (running the Web site) is currently unable to handle the HTTP request due to a temporary overloading or maintenance of the server. The implication is that this is a temporary condition which will be alleviated after some delay. Some servers in this state may also simply refuse the socket connection, in which case a different error may be generated because the socket creation timed out.

One thing that can happen on your server is that all 80+ ports the server receives taking precedence over port 80. The same port your website runs on.

Here's a command to see if this is true (run it in cmd):

netsh http show urlacl

if you get an entry something like this:

Reserved URL : http://+:80/

Then this means that the above issue is happening to you. And you need to remove the record from there with this command

netsh http delete urlacl url=http://+:80/


share|improve this answer

Your first step in determining why this is happening is gathering information.

If you have access to the server physically or via RDP, you can use perfmon to analyze the server performance.

Here are some articles on how to do so (note that these are for 2003, but it really hasn't changed much for 2008/2008 R2):

Using the System Monitor (PerfMon) with ASP.NET Applications (IIS 6.0)

Performance Counters for IIS

After you gather information on what's happening performance wise, you can then begin to isolate the cause.

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.