Last post Sep 26, 2011 04:21 PM by markfitzme
Sep 25, 2011 07:51 AM|Martijn2010|LINK
I published my project on a XP Professional machine with IIS6. By testing the ASP.net/C# project I received by two visitors the message - too many connections from the server. I really don't know what the source is of this message. The SQL connections are
closed at the end of all the queries.
It's a very simple website with a few pages. I don't use stored procedures; I think that makes my website not a lot faster, is that right?
Anyone a solution?
Thank you very much!
Sep 25, 2011 12:54 PM|sridhaar.sree|LINK
The error happens when a number of opened SQL connections are made to the server. You can declare the connection object before the Try catch block and dispose the connection in the finally block. Using stored procedures will improve the performance a bit
faster from database side.
Sep 25, 2011 12:56 PM|Mikesdotnetting|LINK
I published my project on a XP Professional machine
I suspect that's the problem. XP is not a server operating system. However, you should take this question up in the
IIS forums. They share the same membership as this site so you can use your existing credentials to log in there.
Sep 25, 2011 01:02 PM|d.developer|LINK
problem is might be due too multiple connection strings in web.config
Sep 26, 2011 09:30 AM|jayeshgoyani|LINK
increase Max Pool Size in your connction string.
Sep 26, 2011 04:21 PM|markfitzme|LINK
MS Non-Server OSes such as Windows XP were limited to 10 simultaneous connections. That doesn't mean 10 users either. A browser can connect multiple times in 1 session in order to get all the items quickly. Even 1 user could run into this, though not normally.
Also keep in mind, XP Pro is IIS 5.1 so there also may be other issues involved as it does have a few differneces from IIS 6.