Note to self.. it has been too damn long since Pack93z has watched "The Jerk".

Originally Posted by: Pack93z 

Under Construction

There are occassions where a DotNetNuke site displays the underconstruction page and it is not clear why. There are only three specific cases where the under construction page is displayed

1. The system thinks it needs to perform an installation and the AutoUpgrade setting in web.config is set to false.

2. The system thinks it needs to perform a system upgrade and the AutoUpgrade setting in web.config is set to false.

3. The system gets an error when trying to determine if the database version matches the DotNetNuke assembly version.

In all of these cases the display of the page is triggered by the system having difficulty connecting to the db or because the system actually needs to be upgraded because the database is out of synch with the code.

To correct this issue, you should make sure that the latest version listed in the versions table matches the version of the DotNetNuke.dll. If this is correct then you should verify that the application can connect to the database.

Even if those explanations made sense, it still wouldn't explain why it goes down for 8, 10, or even 12 hours. How long can it possibly take for the software to upgrade itself?

Originally Posted by: Nonstopdrivel 

And there is no way to turn off auto-updates? That is truly strange. It is really easy to do in phpBB.

Originally Posted by: Nonstopdrivel 

I don't know where you got the idea that I thought it is phpBB. If it were, the comparison would have made much sense, would it. :-" My point is that phpBB, for all its limitations, makes a lot of things really easy that seem to be more difficult in other packages.

And yes, that thought has occurred to me repeatedly: If this were a commercial business, customers would go away. There have been a number of posts I didn't make because of the downtime.

Originally Posted by: Nonstopdrivel