I started getting this error when I accessed pages hosted on IIS installed on my machine (I’m running Windows XP):
The page cannot be displayed
There are too many people accessing the Web site at this time.——————————————————————————–
Please try the following:
Click the Refresh button, or try again later.
Open the localhost home page, and then look for links to the information you want.
HTTP 403.9 – Access Forbidden: Too many users are connected
Internet Information Services——————————————————————————–
Technical Information (for support personnel)
Background:
This error can occur if the Web server is busy and cannot process your request due to heavy traffic.More information:
Microsoft Support
The wierd thing was I was getting that error on Opera and IE, but everything was fine on Firefox.
Solution
My friend suggested the following:
- go to IIS Manager
- right click on ‘Default Web Site’ (under YOUR_MACHINE_NAME/Web Sites/) and choose properties
- change ‘Connection Timeout’ value to 10 seconds
- uncheck ‘HTTP Keep-Alives Enabled’
- save the changes


This solve the problem, but it could give me another problems???
Hi,
I get the same error, on trying the solution by disabling the HTTP Keep-alives option I get another error message box as follows after few seconds.
—————————
Microsoft Internet Explorer
—————————
Internet Explorer cannot open the Internet site http://localhost/PlgWebHome/TestSection/TestCamera.aspx?.
Operation aborted
—————————
OK
—————————
http://localhost/PlgWebHome/TestSection/TestCamera.aspx? is the url of the accessing page.
what should be done? any help.
Thanks,
without keep-alive NTLM auth. will not work
thank you very much you just saved my bacon
This is not a proper solution, in fact there is solution for this issue because the problem is with the windows OS it self, there are connection limits http://support.microsoft.com/kb/314882
So even if you uncheck keep-alive it just closes the connection after it is processed, but if there are more concurrent request you will get the same error.
Ta,
Rajeesh
Another (simple) option to correct the problem is to just open Task Manager, find ‘aspnet_wp.exe’ and end the process. It will re-spawn and your localhost should be working again.
Thanks so much!!
Thanks it works fine now. Thanks a lot for solution
thanks for the answer this solved my problem
i hope this will help to many people
Thanks, works for me. Excellent.
Thanks , I meeting this problem too. It’s a good solution
as you said find aspnet_wp.exe process and end it. but its not running and there are no users accessing my local application.
so any solution?
Thanks Aaron,
it Solved my Problem.
Thanks Aaron
If you have a proxy open for debugging (like fiddler) this can cause this problem.. close fiddler boom gone