HTTP 403.9 - Access Forbidden: Too many users are connected

[Guest]

When I try logging into my web app using local host I am getting the "HTTP
403.9 - Access Forbidden: Too many users are connected
Internet Information Services". The thing is I do not have 10 users connected!

I have been running Microsoft Application Center Test for load testing
purposes, and also another application called "ANTS Load" for the same
purpose. I don't know if there's any direct relation between doing load
testing with these applications which over-load IIS with HTTP requests and me
getting this error.

The problem is I started getting this problem hours after I stopped running
these tools.

I am running Microsoft Windows XP Pro (SP-1), and I am using Visual Studio
..NET and Microsoft .NET Framework 1.1 (without the service pack installed).

I can't figure out how to fix this any help would be greatly appreciated.
Thanks.

 

[Ken Dopierala Jr.]

Hi,

I get that a lot and I usually just have to refresh the page and it works.
This can happen because when IE loads a page I think it uses up to 3
connections by default. Now if you have frames that gets multiplied by
three. Also some controls like 3rd party drop-down menus and stuff will
create additional connections if they need to. And if you launch popups
there is 3 more connections. Most of the time I don't have a problem, but
if I try to do a ton of stuff without waiting for another browser window to
finish loading and drop its connections I'll get that error. I also rack up
connections because I make extensive use of the webservice.htc. I don't
know a way around it but to reload the page. I don't think you are doing
anything wrong though, if that helps. Good luck! Ken.

 

[Guest]

Well...I finally fixed the problem.

Basically before whenever I got the latest of all my files from VSS I would
not get Web.Config because there was an issue with a log4net error coming up.
I got the latest on Web.Config, re-compiled and it works fine. I still don't
understand how it just started giving me this error out of the blue
though...and all I guess I had to do to fix it was get latest on ALL my
files. Thanks for the help though.