I'm getting this error and it makes no sense:

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.

Note, I'm removing 2 ORM tools: NCI Easy Objects and LLBL.  These were "square-pegged" in without using a proper provider.  I've taken out all but 3 modules using them so it can be I need to finish the job and things will be unstable until I do.

The site is running 4.9, so the whole exercise is being done to get to a usual DNN model so I can upgrade it to the latest stable version.  I did have the modules I've done so far working perfectly.  One of these is a threading application to do searches for parts.  Another note is there is a VERY large search results table I need to trim down from 12 million plus records to only the current year's searches.  I don't think this is an issue.

I get the connection timeout immediately.  It's like the connection never even opened.

The server I'm doing the site dev on also has several production DNN sites but these, even doing the same thing, have their own databases.  The Dev site has its own Database.

I'm not sure what's up but I'm suspecting the ORM tools are the root cause of evil here.  At some point I'd want to reach out with the web.config we have so I can optimize it once the ORM is removed.  So if there's a web.config guru out there, that would be great.

Thanks,

MIke