Click here to Skip to main content
13,149,073 members (53,786 online)
Rate this:
Please Sign up or sign in to vote.
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:

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

we are using the latest blade servers in our
production environment and this started happening after a new website
was hosted. (all websites are hosted in this particular server is having
this problem now ) so could it possibly be due to network traffic??
could anything related to IIS cause this problem???

Any idea why this is happening?
Posted 28-Aug-12 19:55pm
Zoltán Zörgő 29-Aug-12 2:04am
Take a look on the IIS logs related to the site and the windows logs.
@amitgajjar 29-Aug-12 2:18am
this may be possible because of DNS caching. restart your internet router and then try again. it will work for sure.
deepakaitr12345 4-Sep-12 7:47am
check the following possibilities
1)Your connection checkes in reder and other dispose mathod after every transection
2)App pool is not refreshhing set the time in IIS for that.
3)IIS reset(please do not reset the iis it impact on other sites also)
4)compress the css,images and jave scripts(it will help you to load the content as early as possible)

Hope it will help you

Rockstar_ 30-May-13 7:50am
Is ur database is also on the same server?
check for any schedule is running?
otherwise reset the IIS settings...

1 solution

Rate this: bad
Please Sign up or sign in to vote.

Solution 2

The http 503 is probably your biggest clue.

Service unavailable is normally thrown when the application pool is shutdown.

If it was networking you'd most likely get a 500 or a 504.

You can also quite quickly exclude networking as problem by browsing the site from the server.

I would check your event log. You'll most likely find a whole bunch of messages about application pool restarts and worker thread recycling.

This will point to a misconfiguration in your application pool.

If you application pool has a memory threshold for recycling adding additional applications to the same application pool will increase the memory of the worker thread and can force it recycle with nearly every request.

If there are a large number of worker threads recycling it can force the whole application pool to restart.

You can also use the developer tools in your browser to run a network trace. You'll probably notice your style, images and js is missing for the same reason. Your servers response for those resources was a http 503.

My advice would be to configure 1 application pool per application. Ensure you remove any forced recycles because of memory limits. Instead recycle at a 3 / 6 or 12 hour interval.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

  Print Answers RSS
Top Experts
Last 24hrsThis month

Advertise | Privacy |
Web04 | 2.8.170924.2 | Last Updated 6 Jun 2013
Copyright © CodeProject, 1999-2017
All Rights Reserved. Terms of Service
Layout: fixed | fluid

CodeProject, 503-250 Ferrand Drive Toronto Ontario, M3C 3G8 Canada +1 416-849-8900 x 100