This error is caused by depleted database connections in the connection pool.  To resolve the problem, you should

1) Check your application to make sure all database connections are closed when it is not needed.  ASP.NET is supposed to have garbage collector to reclaim unused resource.  However, on a busy site, it is likely that the connection pool will run out of connections before garbage collection kicks in.

2) You can raise the connection pool size in the connection string.  For example, you can add "Max Pool Size=100" to your connection string to increase the pool size to 100.
----------------------------------------------------------------------------------------

Now how would I go about implementing this solution (i.e. checking apps in order to make sure all database connections are closed, rasing the connection pool size, etc...)

Our site is bustling and will do so even more as warm weather kicks in as well as it being on an sql server with a lot of databases connected to it which could have fairly busy activity. 

Is their a way in which you can set a garbage collector to kick in sooner than it might be defaulted to kick in and also I didn't see a max pool size on the web.config file is their a way I can add this.  Lastly how big would you suggest I make the max pool size to be. 

I did talk to my host about this to find out what the allowed max pool limit was they would accept as well as asking them the consequences of setting a max pool high in regards to performance, memory, or other resources bench marks but since they are not really dotnetnuke specialists and just provide asp.net hosting I was wondering if you had any suggestions for me concerning a good max pool to set it at and consequences for setting max pools to high, or too low for that matter though I am sure one of the too low consequences are running out of pools to use.

Thanks,

Bo