Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations wOOdy-Soft on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

IIS 4.0 Error --- Too many users...

Status
Not open for further replies.

knuckle05

Programmer
Dec 17, 2001
247
CA
Hi all,

I'm running an ASP site using IIS 4.0 on a Windows 2000 Professional OS.

When accessing a certain page abc.asp, I get an error with the following line...
Code:
set FSO = Server.CreateObject("Scripting.FileSystemObject")
set objFile = FSO.GetFile server.MapPath(rs("EntireFilePath"))
Anyway, this works fine on the development server, however, upon getting this error, the entire site goes down and you receive the error stating that "Too many users are currently accessing the site". The server must then be re-booted.

If I remove the code, the site functions perfectly. Also, I have checked that the scrrun.dll file is registered and it is, and the max connections allowed on the web server is set to 10 by default and cannot be changed. (Windows specific).

I have made a test ASP page (on the Production server) where I open the AutoExec.bat file using the FileSystemObject and it still hangs the site.

The development server has the capability to allow unlimited connections. Does anyone think that this could be the problem? Any help would be much appreciated. Thanks
 
If you are going to run IIS for a web Server I would definitely recommend putting it on Windows 2000 Server instead of Professional. Is your development box running 2000 server ?
 
yes actually it is.

But do you suppose that this is the source of my problem. Upon further testing, it just seems that the FileSystemObject crashes the system as I have now testes it on other 2000 Professional boxes instead of a 2000 Server.
 
You may want to check and make sure the test machine (that it runs correctly on) and the machine it crashes have the same Service Packs and hot fixes applied to them.
 
thanks for the tip, I'll check it out and report back here what I find.
 
IIS limites the number of connections to 256 multiplied by the number of CPU's. This is by default. To change this behaviour edit the following registry key:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\InetInfo\Parameters\PoolThreadLimit

Change it from 256 to any value you like. Don't increase it too much since it slows down overall system performance.
 
Tank you,
i m searching the solution for this problem too,

tanks a lot, again and again.

it´s now is working,

 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top