I keep getting this error message on my site and I have no clue whats causing it. I have not added any custom code and have only the pre-package DNN modules installed with a few free ones from snowcovered.com.  Generally I can temporarily fix the problem by updating the web.config which causes .net to reload the application again then it works. But then if I go to the homepage without logging, in just click around on the links then leave the page idle for 5-10 minutes then actively click on the links again i get the error below for the entire site. My site is hosted on godaddy and I keep getting weird issues with them. Currently no one is using my site so it can't be creating that many connection pools to cause this error. I working with godaddy support but i'm expecting them to blame the application. There is only one thing that I did change was Module caching method to "Memory" instead of Disk. but would t his cause this??

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

Hi,

    Thanks for your suggestion. I'm going to try and ask if support can check into the two items you mention. But so far like i expected they said it's an application issue and that if it was a server issue moving to a different server with IIS 7 should have helped but it didn't.  I also changed the caching mode back to "disk" and that seem to help but every now and then it still gives me the error.  if i can't fix this issue soon. I'm going be try starting from scratch and delete everything and do a new dnn install with a new database setup. Then if I still get that error I'm saying good bye to godday. 

I'm using dnn 04.09.03

sql server 2005

I had a difficult time when hosting with GoDaddy because of the way their App pools are setup. Turns out the issue was the collective resources of the app pool would increase until the pool stopped responding. Then after the application pool is reset, the site works again until the pool saturates the RAM again. I bought my own server and researched a solution, which turned out to be the following:

Turn on Auto-recycle for the application pool, and set it to something like 75 Megs.

Not sure if this is the same problem you're having... but since updating the web.config seems to make the site work for a few minutes, it's possible. Without having access to IIS, you may call and ask them to try setting that up for you.

P.S. - They WILL blame the application! I called them 5 times for the same problem and one tech said, "I know what the problem is.... Bad code! You need to contact your programmer" I cancelled service 2 days later.

Robert