Hi cc24x7,
I'm not getting the timeouts, but instead getting a bunch of other errors, just over the last few days. That's when I reported a slowdown to my host's support. They made some changes to my app pool, and who knows what else. I think I'm runnung 3.2.2, but for the life of me, I can't remember or how to determine my version number (it's that long-term loss of short-term memory I suffer from).
At this point, I'm fairly sure my problems aren't caused by my DNN installation, configuration, modules, etc. They all appeared after my host tried to fix a slowdown issue. Knowing that logged errors (as well as large logs) will cause slowdowns, I keep my logs cleared regularly and set to log only a few events that I feel necessary to keep an eye on things. With errors cropping up quickly while my host tries to find a remedy I needed a way to clear the logs when I was unable to log in to my portals.
Regarding timeouts, I changed the setting in my web.config to 360 seconds a while back, to allow enough time for synchronizing the database & system files from within the file manager. My child portals, more than 30Mb in size, would timeout on synching. I still get occasional timeouts. Clearing the recycle bins, deleting orphan files, and clearing the cache before synchronizing will usually allow it without error.
If you can log in and get to the scheduler, disable all the scheduled tasks. Then enable them, one at a time, navigate around your portal(s), and check the log. When the timeouts or errors start, disable the last task you enabled and try another one. One or more of the scheduled tasks will reveal itself as the trouble.
Good luck. Thanks for your input, too!
Rick