max pool size was reached

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

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.

This has only happend since upgrading to .net 2003. The application worked
perfect prior to the upgrade. I do not have SQL Server debugging on yet this
error occurs 'EVERY' time it attempt to execute the sql.open()

When I open SQL and look at the process info under current activy, there are
no applications that have a table open other than the master db.

This has got to be a .net 2003 issue. Does anyone have any clues!
Ken Ray
 
Do you have the pool size specified in the connection string? Also, run
SPWho and see who's all in the db - The 1.1 framework has been quite stable
so I doubt it's simply this that's causing it
 
Back
Top