Hello Stephanie,

I didn't see this problem before, so I couldn't tell exactly what happens.
However, you could try to use the following methods to monitor connection
pooling in the system:

To monitor your application's use of connection pooling, you can use the
Profiler tool that ships with SQL Server, or the Performance Monitor tool
that ships with Microsoft Windows 2000.

To monitor connection pooling with SQL Server Profiler

1) Click Start, point to Programs, point to Microsoft SQL Server, and then
click Profiler to start Profiler.
2) On the File menu, point to New, and then click Trace.
3) Supply connection details, and then click OK.
4) In the Trace Properties dialog box, click the Events tab.
5) In the Selected event classes list, ensure that the Audit Login and
Audit Logout events are shown beneath Security Audit. To make the trace
clearer, remove all other events from the list.
6) Click Run to start the trace. You will see Audit Login events when
connections are established and Audit Logout events when connections are
closed.

To monitor connection pooling with Performance Monitor

1) Click Start, point to Programs, point to Administrative Tools, and then
click Performance to start Performance Monitor.
2) Right-click the graph background, and then click Add Counters.
3) In the Performance object drop-down list, click SQL Server: General
Statistics.
4) In the list that appears, click User Connections.
5) Click Add, and then click Close.
Note The RTM version of the .NET Framework will include an additional set
of ADO.NET performance counters that can be used in conjunction with
Performance Monitor to monitor and accumulate connection-pooling statistics
for the SQL Server .NET Data Provider

Hope it helps.

Best regards,
yhhuang
VS.NET, Visual C++
Microsoft

This posting is provided "AS IS" with no warranties, and confers no rights.
Got .Net? http://www.gotdotnet.com
--------------------
!Content-Class: urn:content-classes:message
!From: "Stephanie" <sreed (AT) co (DOT) slo.ca.us>
!Sender: "Stephanie" <sreed (AT) co (DOT) slo.ca.us>
!Subject: Pooled connection error
!Date: Fri, 20 Jun 2003 07:24:07 -0700
!Lines: 16
!Message-ID: <0ba301c33737$9ba078e0$a501280a (AT) phx (DOT) gbl>
!MIME-Version: 1.0
!Content-Type: text/plain;
! charset="iso-8859-1"
!Content-Transfer-Encoding: 7bit
!X-Newsreader: Microsoft CDO for Windows 2000
!Thread-Index: AcM3N5ugxepHeLFcS9qbyIkWneY6RQ==
!X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4910.0300
!Newsgroups: microsoft.public.dotnet.distributed_apps
!Path: cpmsftngxa06.phx.gbl
!Xref: cpmsftngxa06.phx.gbl microsoft.public.dotnet.distributed_apps:5869
!NNTP-Posting-Host: TK2MSFTNGXA13 10.40.1.165
!X-Tomcat-NG: microsoft.public.dotnet.distributed_apps
!
!After installing VS2003 Frame work 1.1 we are recieving
!the following error. No application code was changed.
!
!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.
!
!I know I can increase the pool size, but doesn't fix the
!problem. We are running our application on both an
!internet and intranet site. The internet site has not
!been updated yet and is working fine. On the intranet we
!are only about 25 users.
!
!Any Ideas?
!Thanks, Steph
!