Error:max pool size was reached

Hi!
Since I installed the Visual Studio 2003 I got a problem:
every few hours I got an error that I can't open the
connection to the SQL Server database:

"Timeout expired. The timeout period elapsed prior to
obtaining a connection from the pool. This may have
occurred because all pooled connections were in use and
max pool size was reached. "

then I must run IISRESET before I can continue.

* I must mention that : All that stuff Worked ok until I
installed the Visual Studio 2003.

Thanks For Eny Help
hergass

Paul
Sun Dec 07 10:25:41 CST 2003

On Sun, 7 Dec 2003 01:49:18 -0800, "Hergass" <hergass@yahoo.com>
wrote:

>Hi!
>Since I installed the Visual Studio 2003 I got a problem:
>every few hours I got an error that I can't open the
>connection to the SQL Server database:
>
>"Timeout expired. The timeout period elapsed prior to
>obtaining a connection from the pool. This may have
>occurred because all pooled connections were in use and
>max pool size was reached. "
>
>then I must run IISRESET before I can continue.
>
>* I must mention that : All that stuff Worked ok until I
>installed the Visual Studio 2003.
>
>Thanks For Eny Help
>hergass

Hello,

Try these articles :

http://www.maximumasp.com/maxtrack.asp?kb=432

http://www.schmiddy.net/blog/2003/10/connection_pool.html


Regards,

Paul Lynch
MCSE

v-wdxu
Tue Dec 09 03:10:51 CST 2003

Hi Hergass,

Thank you for posting in MSDN managed newsgroup!

So far as I know, this issue may be related to the internal implementation of SQL connection objects. I'd suggest the kb article 830118 may provide
some assistance for you on this issue which introduces two workarounds for us with sample codes regarding this error message. Please go to:
830118 PRB: "Timeout expired" Error Message When You Run a Visual Studio .NET
http://support.microsoft.com/?id=830118

Please feel free to let me know if you have any further questions.

Does this answer your question? Thank you for using Microsoft NewsGroup!

Wei-Dong Xu
Microsoft Product Support Services
Get Secure! - www.microsoft.com/security
This posting is provided "AS IS" with no warranties, and confers no rights.

Bernard
Tue Dec 09 04:02:14 CST 2003

KB not available, Wei-Dong.

--
Regards,
Bernard Cheah
http://support.microsoft.com/
Please respond to newsgroups only ...



"Wei-Dong Xu [MSFT]" <v-wdxu@online.microsoft.com> wrote in message
news:jRC5jRjvDHA.3972@cpmsftngxa07.phx.gbl...
> Hi Hergass,
>
> Thank you for posting in MSDN managed newsgroup!
>
> So far as I know, this issue may be related to the internal implementation
of SQL connection objects. I'd suggest the kb article 830118 may provide
> some assistance for you on this issue which introduces two workarounds for
us with sample codes regarding this error message. Please go to:
> 830118 PRB: "Timeout expired" Error Message When You Run a Visual Studio
.NET
> http://support.microsoft.com/?id=830118
>
> Please feel free to let me know if you have any further questions.
>
> Does this answer your question? Thank you for using Microsoft NewsGroup!
>
> Wei-Dong Xu
> Microsoft Product Support Services
> Get Secure! - www.microsoft.com/security
> This posting is provided "AS IS" with no warranties, and confers no
rights.
>
>

v-wdxu
Tue Dec 09 21:32:25 CST 2003

Hi Bernard,

Thank you for your reminding!

Since this article is not available now, I have mailed one mail to Hergass concerning this.

Thank you for using Microsoft NewsGroup!

Wei-Dong Xu
Microsoft Product Support Services
Get Secure! - www.microsoft.com/security
This posting is provided "AS IS" with no warranties, and confers no rights.

v-wdxu
Tue Dec 09 22:09:11 CST 2003

Hi Hergass,

Thank you for posting in MSDN managed newsgroup!

Since my mail for you has been sent back by the yahoo mail system, I will try to provide some assistance for you on this issue.

One workaround:
Change the Debug mode configuration properties of the project. Please follow these steps:
1. In Visual Studio .NET, right click your application in Solution
Explorer, and then click "Properties".
2. In a Microsoft Visual Basic.Net project, Click "Debug" under "Configuration Properties",
and then clear "SQL Server debugging" under "Enable Debuggers".
In a Microsoft Visual C# .NET project, click "Debugging" under "Configuration Properties",
and then set the value of "Enable SQL Debugging" under "Debuggers" to "False".

The second workaround:
Change the project configuration to Release mode. Plesae follow these steps:
1. In Visual Studio .NET, click "Configuration Manager" on the "Build"
menu, and then click "Release" in the "Active Solution Configuration"
list.
2. On the "Debug" menu, click "Start" to run your application. Notice
that you do not receive the error message that is mentioned in the
"Symptoms" section of this article.

Please feel free to let me know if you have any further questions.

Does this answer your question? Thank you for using Microsoft NewsGroup!

Wei-Dong Xu
Microsoft Product Support Services
Get Secure! - www.microsoft.com/security
This posting is provided "AS IS" with no warranties, and confers no rights.

google
Thu Dec 18 04:51:40 CST 2003

Hi Wei-Dong,

I'm having a similar problem. I've developed an intranet that has
given this error message twice in a couple of months of running, once
on the live system, and once on a test system.

I've checked through the code, and am pretty sure I close all DB
connections either explicitly, or automatically after a DataBind call
(I always use CommandBehaviour.CloseConnection.) I've also used
performance monitoring to monitor the .NET CLR data counters, and this
shows the total number of pooled connections to be static at 4. I was
half-expecting to see this slowly rise - if I had a resource leak -
but it doesn't.

The second time this happened, I tried to open a SQL query window to
run sp_who, but it wouldn't open completely. In the end, I stopped the
aspnet_wp process, and everything was then OK.

I may have to automatically recycle the aspnet_wp processes
occasionally. I'm loathe to do this though, as the data stored in the
session state will be lost, and that will inconvenience the users.

The project is built in release mode, and SQL debugging is disabled.


Is this a known bug in .NET? I've seen a lot of posts about this, but
none seem to find the root cause.