Warning: Table 'mydatabas.access' doesn't exist query: SELECT 1 FROM access WHERE type = 'host' AND LOWER('127.0.0.1') LIKE LOWE

By droopypal on 17 May 2009 at 05:11 UTC

I had no problems with 6.11, but with 6.12 I get this when I try to run browser for first time:
(my database is named btplanner)

Warning: Table 'btplanner.access' doesn't exist query: SELECT 1 FROM access WHERE type = 'host' AND LOWER('127.0.0.1') LIKE LOWER(mask) AND status = 0 LIMIT 0, 1 in C:\wamp\www\btplanner\includes\database.mysql.inc on line 128

Warning: Table 'btplanner.cache' doesn't exist query: SELECT data, created, headers, expire, serialized FROM cache WHERE cid = 'variables' in C:\wamp\www\btplanner\includes\database.mysql.inc on line 128

Warning: Table 'btplanner.variable' doesn't exist query: SELECT * FROM variable in C:\wamp\www\btplanner\includes\database.mysql.inc on line 128

Notice: Undefined variable: variables in C:\wamp\www\btplanner\includes\bootstrap.inc on line 480

Warning: Table 'btplanner.cache' doesn't exist query: UPDATE cache SET data = '', created = 1242536894, expire = 0, headers = '', serialized = 0 WHERE cid = 'variables' in C:\wamp\www\btplanner\includes\database.mysql.inc on line 128

Notice: Undefined variable: variables in C:\wamp\www\btplanner\includes\bootstrap.inc on line 487

Warning: Table 'btplanner.system' doesn't exist query: SELECT name, filename, throttle FROM system WHERE type = 'module' AND status = 1 AND bootstrap = 1 ORDER BY weight ASC, filename ASC in C:\wamp\www\btplanner\includes\database.mysql.inc on line 128

Warning: Table 'btplanner.url_alias' doesn't exist query: SELECT COUNT(pid) FROM url_alias in C:\wamp\www\btplanner\includes\database.mysql.inc on line 128

Comments

The error messages say that

cog.rusty commented 17 May 2009 at 07:37

The error messages say that Drupal reads the btplanner database but it can't find its tables in it. Go to the database with phpmyadmin and check:

- Do the tables "access", "cache", "variable", "system", "url_alias" exist or not?
- Are the names of the tables in the database correct, or do they have some prefix in front?

Thanks for your help: The

droopypal commented 17 May 2009 at 15:49

Thanks for your help:

The database is empty.
The error occurs when I first try to load the site, before I select the English language.
I don't know why there is an attempt to read the database at this point since I am not at that step.
This never happened with 6-11.
I DO have my settings.php setup properly...hmmm...perhaps I have done that too soon.

THAT WAS IT! DON'T CREATE SETTINGS.PHP BEFORE SELECTING LANGUAGE

droopypal commented 17 May 2009 at 15:55

The error was caused by my setting up settings.php before choosing English as my language.
When I deleted my settings.php file...I got the initial select language page.

So...my successful earlier experience with Drupal caused the problem!

Thanks goodness...wasted a day on this issue.

Thanks for the help, I'm

omc commented 17 May 2009 at 21:56

Thanks for the help, I'm getting the same issue and it was annoying the heck out of me... I ended up exporting another drupal install and then importing it for a new site setup as the installer was not working at all.

This is obviously a much better way to do it :D

Ironic too, as I had to add these lines to my settings.php file so I could find out why it was erroring:

ini_set('display_errors', 1);
ini_set('log_errors', 1);
ini_set('error_log', dirname(__FILE__) . '/error_log.txt');
error_reporting(E_ALL);

Thanks wasted my time to think

v1p3r1c3 commented 10 November 2009 at 08:33

I move the settings.php outside the default folders and move back after the language part

thanks buddy

gyaan commented 29 August 2010 at 10:47

i have same error when i install the fresh copy of the drupal 6.19 . just start installtion without create setting.php file and created after language selection than installation complete without any error

thanks a lot you people for help

Hi

namjoo commented 20 July 2014 at 05:47

This work for me on Centos.
Thanks all

Thanks!

eliasdelatorre commented 11 July 2012 at 23:44

Hey, thanks for posting this, I was completely lost since looking for the problem is kind of complex, given that no information is widely available.

I even thought that I had a problem with my DB permissions.

But yeah, this worked. I moved my settings.php file to another location and after that the installation started working, then I moved back the file.

Thanks guys I was really, really lost.

Cheers!

This needs to be reported as a bug.

Rewted commented 11 June 2009 at 18:53

Confirmed. Going to the site URL before creating the settings file and selecting your language first gets around this error.

this helped a ton

krisvannest commented 6 September 2009 at 18:04

THANK YOU for posting this-- ran into same prob with fresh 6.13 install, hadn't seen the problem before under 6.xx prior, so had no idea what to do next until reading this post showed solution. thx

Same on 6.14

mamasdiner commented 17 October 2009 at 04:30

Same error on fresh install of 6.14. Deleted the settings.php file, selected English then copied settings file back and no problems.

Thanks so much for the help!

same here with 6.14

garbo commented 1 December 2009 at 09:56

Never experienced this issue untill today.

Couldn't tell what's causing it. I have several succesfull installs in the same host.

I had the same problem when

4aficiona2 commented 4 December 2009 at 10:02

I had the same problem when installing open publish. actually I've installed several other Drupal websites before, but did not run into this error.

The solution for me was as well to reset the database settings in settings.php which I entered to early (manually by text editor) ...

So the entry looked like this,

$db_url = 'mysql://dbusername:dbpassword@localhost/drupal_openpublish';

instead of

$db_url = 'mysql://username:password@localhost/databasename';

Thanks a lot, it worked perfectly for me.

P.S.: dbusername, dbpassword got actually replaced for this post

This is the one causing problem

jwalantsoneji commented 19 August 2010 at 20:00

Well, I was following the Windows, PHPMyAdmin and Linux was which is described on the main page of the installation documentation; and that's why edited the config.php in text-editor.
Since then was getting the same error.

As soon as I replaced the one with the original file, the problem is solved.

Thanks a lot!

Weird...

Ellen Dee commented 27 February 2010 at 18:01

I install one or two of these a week (on Wampserver) and today I got these errors for the first time. Same thing-- selecting language, first, solved the problem. Version is 6.15-- third one installed this week. Can't wrap my head around what I might have done differently, but it must be something. Anyway, thanks for pointing us to a workaround.

Absolutely Wierd

drwierdo commented 18 March 2010 at 10:52

i too install drupal so many times every week.......but never got this problem until today...i am using drupal 6.16....but this work around did work...thanx..had been scratching my head over this problem for the whole day.....thanx

Same error -Drupal 6.16

hip commented 14 April 2010 at 14:52

Same error -Drupal 6.16

DON'T CREATE SETTINGS.PHP BEFORE SELECTING LANGUAGE

zbombicz commented 20 April 2010 at 06:35

DON'T CREATE SETTINGS.PHP BEFORE SELECTING LANGUAGE

I am still getting this error

imoria commented 17 May 2010 at 01:30

I am still getting this error and removing the settings.php file and doing install in english and putting it back in didn't help it. Any suggestions?

.

cog.rusty commented 17 May 2010 at 02:20

Why did you put it back? Didn't your installation create a settings.php file that worked?

"Didn't your installation create a settings file that worked?"

beanluc commented 7 June 2010 at 01:50

Well, no, and, yes. But the problem isn't related to this, as I will show below.

I never had this problem before today - first time installing new 6.17 site.

If I don't create the settings.php file until after choosing the language, then, I get
"

Requirements problem
The following error must be resolved before you can continue the installation process:

The Drupal installer requires that you create a settings file as part of the installation process. 
Copy the ./sites/default/default.settings.php file to ./sites/default/settings.php.

So: no, Drupal isn't creating a settings.php file that works - it's asking me to create the file.

When I do that, and proceed through the "Set up database" step, I get the original error reported by many above. Drupal does update my settings.php with the DB info, but, somehow only 40 tables got created, not inlcuding the 'access' table and others named above.

So: Yes, after I create settings.php at the proper step (after Language selection)
, then, Yes, Drupal can write DB settings into it and clearly can execute at least some DB operations (creating 40 tables).

So, I'm still stuck. I have the exact same symptoms as everyone else above, but, the "wait to set Language, then create settings.php" instruction doesn't help me.

Again, I'm suspicious of the fact that I'm creating a new site for the first time using 6.17. I've done new sites with earlier versions, and, I've updated sites to 6.17, but first time installing anew from 6.17.

.

cog.rusty commented 7 June 2010 at 02:19

I have never encountered a "wait for language" problem myself either.

Have you checked PHP's memory limit? (Although it is hard to imagine a limit lower than the 16M which core requires these days).

There must be something in PHP's or Apache's error logs. Maybe a timeout.

Yes: timeout

beanluc commented 18 June 2010 at 20:15

You're right on, cog.rusty,

Raising max_execution_time in php.ini solves the problem.

Deployment in another environment

xjkwak commented 2 August 2010 at 13:36

I tried to deploy my drupal site in another environment (it's not a new installation, just deployment of an existing site in another environment); however I get this problem. I tried all your suggestions but the problem persists.

Any ideas?

Thanks in advance.

I solved this problem by creating the 'access' table.

xjkwak commented 5 August 2010 at 19:15

I created that table empty with the fields that are required and it works!.

The script table should be:


CREATE TABLE IF NOT EXISTS `access` (
  `id` int(10) unsigned default NULL,
  `type` varchar(10) default NULL,
  `mask` varchar(10) default NULL,
  `status` int(10) unsigned default NULL
) ENGINE=InnoDB DEFAULT CHARSET=latin1;

I hope this is useful for others.

(solved) Check the sql-import

vader111 commented 21 August 2011 at 17:41

Pha! I had the same problem. I was trying to restore a backup of an online working drupal site onto my local wamp server. Got the files and got the sql-import data.
Got the errors too.

Solution: Then got the idea that in the process of setting up the database I was forgetting... to import the sql-tables.

Don't read installation instructions and don't execute queries before making sure you are not forgetting something silly. *golden rule*

I am using version 6.19. I

Jumoke commented 17 August 2010 at 05:02

I am using version 6.19. I got this error too.
Removing the db settings from settings.php fixes this for me.

Removing settings.php works. Should Drupal 6.x warn users first?

Andy B commented 17 August 2010 at 12:17

I had a 6.19 install on a production site that I was setting up in a private section until it could go live. I found out that installing over 90 modules and enabling them all creates a navigation menu with around 510 entries. I wanted to change it around and sort it out, but it kept crashing the server (shared hosting server too). My hosting provider timed it: took over 4 hours to load the admin/build/menu/customize/navigation page. Their logs also said that during that 4 hour span of time, the drupal install created and executed around 9000 database queries. None of them looked suspicious which is a good thing. Anyways, I needed to edit the menu so decided to port it over to the dev server (local computer I actually sit at) and work on the menu there. For some reason, it still took around 4 hours to load the page creating 9000 database queries. I decided to start over on the dev server. I took my previous settings.php file and copied it into the folder sites/default and ran the installer to find out the errors at the top of this thread showed up. I am wondering if Drupal can somehow detect that

1. There is a modified version of settings.php that was intended to be used
2. Check to see if this is a clean install or an upgrade (if it can't tell, always better to ask the user). "Drupal has found a modified version of settings.php in sites/default. Do you want to use it during the remainder of the install process?" [answer choices]: "Yes, use it to install drupal", "No, start over with a new settings.php file".

Either way, it seems strange that you need to manually fuss with the settings.php file. Even 7.x forces users to do this. Not everyone who installs drupal knows about (or trusts themselves) with this sort of file manipulation.