I've copied the site files and database down to my local machine and set everything up from scratch.  Still all portals work locally except for the problem one.  I then tried to add the "source" version of DNN in hopes that I could do some debugging.  There seems to be files missing from the source version and I can't get it to compile...  Is there any way else that I can tell what DNN is doing?  When running the site locally, I can see that what's happening is that the portal just runs and never returns anything.  It's like it's stuck in an endless loop or something.  I'm at a total loss.  This is a nightmare!

Just a thought....

Try one or more of the following

Under Host Settings/Advanced Settings/ Other settings:

* Clear cache button
* Change Performance settings to no cache.

If you can, try disabling cache on the modules of the site, if you find the problem to be with a particular module reenable the cache under host settings.

Oh and you're probably do no harm making a backup first.

I've had problems before with caching on the 4.x versions, and I've had to disable caching on many of my modules. I got the exact symptoms you describe on some of my modules.

Another thing to consider is upgrading to 4.3.5 which will be released this month, it will solve a heck of a lot of bugs, although there will still be a lot of issues which I hope can be cleared out in 4.3.6.

Cheers

Alex

---

---

---

I've found the source of the problem.

After giving up on fixing the portal after 9 days of labor, I started over creating a new portal from scratch on a fresh new install of 4.3.4.  As I mentioned in my original post, I suspected a problem with the Blog module.  Well, after getting much of the portal back to it's original state I crossed my fingers and added the Blog module back in.  Everything seemed to work fine for about an hour and then the original "request timed out" problem re-appeared...  Out of disgust and the thought of having to repeat all of my work, I went to bed.  The next morning I woke up and prayed for a different result...no such luck.  So, then I had an idea that had not occurred previously.  I uninstalled the Blog module from DNN totally.  IT WORKED!!!  I don't know exactly what about the Blog module caused the problem.  I (and many other) had used the module on other sites without any problems (on v3.2.3).  It may be a setting (or combination of settings) that I was using or maybe it's something in the HTML that I put in the blog (nothing unusual...).  But there is definitely a serious problem that will render entire portals useless. 

I've had no luck so far, but as soon as I can get a "source" version of DNN up and running I plan to continue to track down the source of this problem so that a fix can be included in a future version.  But, in the meantime, the Blog module will not be reinstalled into any of my DNN instances. 

Anyone have any suggestions for alternative Blog modules?