Re: SQL Server connection Pool error in Debug

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

That fixed my problem. Thank you!
--
Jerry J


"Cowboy (Gregory A. Beamer)" wrote:

Copied from my answer in microsoft.public.dotnet.framework.aspnet:

------------

My guess: The timeout is happening in the SQL debugger itself.

Solution:

Right click the solution and choose Properties
Click Debug (or Debugging) under Configuration Properties

If VB.NET
Find Enabled Debuggers and clear the SQL Server Debugging checkbox

If C#
Find Debuggers and Change Enable SQL Debugging to false

These dialogs were designed by the language teams.


--
Gregory A. Beamer
MVP; MCP: +I, SE, SD, DBA
http://gregorybeamer.spaces.live.com

*********************************************
Think outside the box!
*********************************************
"Jerry J" <JerryJ@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:35FD60EF-EE15-489E-80C0-D487A6935996@xxxxxxxxxxxxxxxx

In my ASP.net application I am getting the following error...

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

This only happens when I am in debug mode. If I run SP_Who in Sql Server I
do not see many open connections. This also NEVER shows up if I run the
web
application from the browser.

I cannot get this to occur if I run line by line in debug mode. I must let
it go without stopping. I cannot narrow down the location in debug either,
because it is not consitant.

I have tried increasing the timeout but that doesn't help. It just hangs
until the timeout has expired.

Searching the internet I have found others with this problem but cannot
find
a solution.


--
Jerry J

.

Relevant Pages

  • Re: SQL Server connection Pool error in Debug
    ... "Jerry J" wrote in message ... The timeout is happening in the SQL debugger itself. ... Click Debug (or Debugging) under Configuration Properties ... > I cannot get this to occur if I run line by line in debug mode. ...
    (microsoft.public.dotnet.framework.adonet)
  • Re: SQL Server connection Pool error in Debug
    ... The timeout is happening in the SQL debugger itself. ... Click Debug (or Debugging) under Configuration Properties ...
    (microsoft.public.dotnet.framework.adonet)
  • Re: SQL Server connection Pool error in Debug
    ... The timeout is happening in the SQL debugger itself. ... Click Debug (or Debugging) under Configuration Properties ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: multithreaded debugging
    ... debugging relies on the state of other threads (and it must or you wouldn't ... have this complaint) then the results in debug mode would be invalid. ... > out to INFINITE works around the problem without solve it because the real ... >> the same behavior on INFINITE timeout? ...
    (microsoft.public.windowsce.platbuilder)
  • SQL Debugger doesnt do anything
    ... visual studio. ... I am debugging from query analyzer. ... SQL debugger just ...
    (microsoft.public.sqlserver.setup)