Add new comment

Database problems could be caused by some form of corruption (bad file, missing key data, disk error...) or a logical issue (tables bloated with orphaned rows, inefficient queries, overdue routine db logfile purging...). The thing is, these problems should throw ODBC errors as long as the database service provider is still running. Of course if the service is busy processing, the errors may not show up before the web service times out on the query. Then I'd expect to see a proper error page served (like the "not set up" error you mentioned). So, when there is no error message at all, I suspect one of two things:
1. Host problems / throttling / server unavailability.
2. Problems with the page scripts (TikiWiki) causing a memory leak or the web service to lock-up and be unavailable for processing requests.

Without access to server logs for troubleshooting, I doubt there is much more that could be said...