thanks for the suggestion... I've implemented some of the ideas I found at Mitch's site - this seemed to help last night, but as of this morning, it's broken... again...
I posted on their forum as well, but perhaps someone here has another suggestion? Here's what I posted. Thanks again.
I have a page (it is a shop locator using google maps and an off site database) that worked until yesterday afternoon albeit always very very slowly. Now, if I try to access the page, it just spins and spins and eventually spits back a generic "turn customErrors Off" message. (even tho customErrors ARE off in my web.config file...)
If I go to Host Settings and Restart Application, the page will load super-quick for a short period of time (across multiple browsers on different machines), but then it will start to fail again.
Last night, I was reading an article on this site and changed the (Host) Performance Settings to the suggestions found here (Heavy Caching and Module Caching = Memory), restarted the application, and everything looked good for maybe an hour or so until I finally passed out from frustration with dnn.
Got up this morning, and the page was still refreshing but, by the time I got to work, it was broken again.
I am now able to restart application and have the page stay active for maybe 5 minutes (vs maybe 1 minute yesterday), but obviously that's completely unacceptable. Sometimes I will now get a "[HttpException (0x80004005): Request timed out.]" message instead of the generic message, but the result is the same... FAIL.
Thanks...