Showing posts with label maximum. Show all posts
Showing posts with label maximum. Show all posts

Friday, March 9, 2012

Error 500, Maximum concurrent users have reached

We are running three web sites in a clustered environment
WLBS. The web servers are connected to a Database Server
running MS SQL server enterprise edition licensed as per
CPU license. The Windows 2000 Advanced Server Licensing
mode on all the servers is per SEAT license.

Our customers are accessing our web servers and after some
time getting error 500, Maximum concurrent users have
reached.

We have been told by our software provider that the
connection problem lies with the ADO components which
communicating with the SQL server.

We have been turning round and round, without any luck.

Your help will be highly appreciated.

Thanks and best regards

Dave

Learning is a Never Ending process

*** Sent via Developersdex http://www.developersdex.com ***
Don't just participate in USENET...get rewarded for it!Dave Kissoondoyal (network@.bowmans.intnet.mu) writes:
> We are running three web sites in a clustered environment
> WLBS. The web servers are connected to a Database Server
> running MS SQL server enterprise edition licensed as per
> CPU license. The Windows 2000 Advanced Server Licensing
> mode on all the servers is per SEAT license.
> Our customers are accessing our web servers and after some
> time getting error 500, Maximum concurrent users have
> reached.
> We have been told by our software provider that the
> connection problem lies with the ADO components which
> communicating with the SQL server.

A message that starts with a three-digit number with a leading 5
looks like a response code from a protocol that sits on top of
TCP/IP. That is, I would assume that this message comes from the
web server and not SQL Server.

Whether the web server reacts this way due to some error code
from SQL Server, I don't know. But it seems that you will have
to investigate the web server first.

--
Erland Sommarskog, SQL Server MVP, sommar@.algonet.se

Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techin.../2000/books.asp

error 500 maximum concurent users have reached

We have three Windows 2000 web servers in a WLBS environment accessing a DB server. Though we have only 180,140 and 40 connections respectively on the servers we received ERROR 500 - maximum concurent users have reached.

Please help us to identify the problem.

Best regards

Network BowmansYou may have only 300 users on the website, but the web pages themselves could be opening hordes of connections. Two things to check would be the license for SQL Server (in control panel should be a license applet for SQL Server). Check to see if you have entered 500 CALs. If you have set the server up as per-processor license, or if you have plenty of cals entered on the system, you can check in Enterprise manager to see how many connections are allowed. Right click on the server, then properties, then the connections tab. Make sure the max connections is set to 0 (unlimited). 0 is the default, and I have not had any problems with it, so far. Hope this helps.|||Hmm. After reviewing the post, I seem to have mistaken the error number for a parameter. Looks like my suggestion may not help after all. Are you certain this is a DB error, and not a web error? Check the SQL Error log to be sure.