Hi,

I installed the table wizard module but when I go to the table wizard settings page at admin/content/tw, I get the following message:

The site is currently not available due to technical problems. Please try again later. Thank you for your understanding.

The settings.php file is set up as specified by the documentation.

I have tried updating to the latest dev version of the module.

What is the source of this problem?

My setup is the following:
Table Wizard 6.x-1.x-dev
Views 6.x-2.8
Schema 6.x-1.6
Drupal 6.14
Apache 2
PHP 5
Mysql 5

Thanks for any info on this.

CommentFileSizeAuthor
#3 table_wizard_error.png4.32 KBh3000
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

h3000’s picture

Title: Site Unavailable error with going to admin/content/tw page » Site Unavailable error when going to admin/content/tw page
mikeryan’s picture

Status: Active » Postponed (maintainer needs more info)

Was there another message below the one you provided? This message is caused by a fatal database error, and there should be more information provided - it comes from the Drupal function _db_error_page(), and all calls I can find to that function provide an additional message.

Can you be more specific on your PHP/MySQL versions?

h3000’s picture

FileSize
4.32 KB

PHP 5.2.6-2ubuntu4.1
Mysql 5.0.67

There were no other messages

Attached is a screenshot of the error message.

Thanks.

mikeryan’s picture

Please make sure you have display_errors turned on in your php.ini or .htaccess - I had missed that this is necessary for the DB error to show.

Thanks.

mikeryan’s picture

Status: Postponed (maintainer needs more info) » Closed (fixed)

No further information provided.

wweibel’s picture

i was having the same problem recently and it would appear that it is an issue while attempting to connect to the external databases. either improper credentials or user login restricted to be from a specific ip address.

a problem that i had a couple times is with passwords containing a ":" - needs to be changed to "%3a"
- during parsing drupal becomes confused since the colon delimits the login creds

also, other issues may result from this as is talked about here http://drupal.org/node/1028730#comment-4876336