Serious IIS problem! Too many connections?

I had this problem before when developing ASP-pages and I switched to "Windows 2000 Server" just to get rid of it, but now I'm back on Windows XP Pro with IIS 5.01 and the problem persists. I've written to several message boards before about this but no one has been able to figure out what the problem is.

The problem is that when I’m experimenting with a site at home from localhost, after about 10-20 minutes (or maybe 20-30 refreshes of the page) I get this error when I refresh the page: “Too many users connected”. And then, before I can continue to work I have to stop the “World Wide Web Publishing” service and then restart my IIS. Often this is not enough and I have to restart the computer. Obviously this is devastating for my work efficiency and I simply have got to resolve this issue as soon as possible because a server OS is not an option anymore. I’m sticking with XP and all I ask is to be able to work on my ASP-pages locally without interruptions.

So I would really appreciate if anyone could give me _any_ information about this at all. What normally causes this? Could some ASP code be the cause, and if so, what code? I’ve checked that I close all my connections properly so I don’t think that’s the problem, and this even happens on pages where no connection objects are initiated.

Some specs: Windows XP Professional, ASP 3.0, IIS 5.01, MySQL 3.23.49.

I've never experienced this problem so I'm not sure if this will help but it's something to look at. Unfortunaly I'm running full IIS not a PWS cutdown which you probably are so options may differ slightly, but:

Under the Internet Services Manger, right click on the website and choose properties.

Under the website tab of the resulting window you will see a scetion about connections.

Here there is an option to limit the number of concurant connections to the site, usually used to protect bandwidth. Set this to unlimited if it is not already.

If there is a limit set, it is possible that this limit could be reached, especialyy during development when your regually refreshing your page. Another approach might be to redce the connection time-out so the become free quicker.

If this doesn't help then let me know, I might have come up with something else...

Maybe you have a developer version of IIS (most times if you get it for free). they are limited to 10-30 connections i think. try to find an option to turn off "persistent connections" / "http-keepalive". then you should have no more problems locally.

... and the two solutions do not work. Did you solve the problem? if so, how?
My problem is when accessing files on the hard disk with ActiveXObject("Scripting.FileSystemObject") in ASP with JavaScript.
I do not have any BD connection.
My specs: Win XP Pro, ASP and JavaScript as server language, free IIS 5.1 that comes in the Win XP Pro cd.

Thank you.

I wrote this down in a textfile which is now gone, but if I remember correctly I solved it by unchecking "HTTP Keep-Alives Enabled" in the IIS Console's website properties.

Please tell us if it solved the problem.

Thank you for your answer, but it was the first thing I've tried and it doesn't work. It seems it keeps working a little more time but at the end, the http 409.3 error apperars again. I am developing an asp website and I am testing one page verymanymany times once and again. I try to restart iis and a couple of times it restarts but next time it gets hanged and i had to restart the computer... It is so irritating... you know.

W2K Pro and XP Pro IIS has a hardwired 10-connection limit. Your testing is probably creating multiple sessions and you exceed 10 before they start timing out. You could try adding an explicit sessionl.abandon where appropriate when you're done with a session. Or try shortening the timeout in IIS, by default sessions remain for 20 minutes before timing out on their own.

You may see a setting in the IIS service manager where you can specify the number of connections, but this setting has no effect in a workstation version of IIS. The connection limit is hard-coded in the program.

Actually, PWS for W9x/Me doesn't have the 10 connection limit as far as I know. But NT4/2K/XP workstation versions of IIS does.

I think we all understand that we're limited to 10 connections, it's not a hard concept. What we are trying to figure out is why we're using up all the connections while testing.

I had the same problem as nuwi (failure to create ActiveXObject), but found that the solution below worked for me (disable Norton Antivirus script blocking).

extracted from URL

Author: ACB
E-mail: URL
Date: 5/19/2003 12:04:25 AM
Subject: Re: IIS 5.1, Windows XP and FileSystemObject Pr...
Message: Do you have an antivirus (like Norton Antivirus) with Script Blocking enable? Try to uncheck it.

Best regards
Alejandro

Will Windows Server 2003 have unlimited connections for IIS?

jonathanhe, yes.

Pikachu420, I think .net allows for more fine tuning of the server's properties on a page by page basis. It can be installed on the free version of IIS.