This forum is no longer active. Please post your questions to our new community site
Drupal 7 Install Problems
|
|
Hi all, tried installing Drupal 7 both from the full wamp installer and drupal module installer and the standalone wamp+drupal installer. Each time when i try and start Drupal i get the following error “PDOException: SQLSTATE28000 1045 Access denied for user ’bitnami’@’localhost’ (using password: YES) in lock_may_be_available() (line 165 of C:\BitNami Drupal Stack\apps\drupal\htdocs\includes\lock.inc).” The only think i am changing from the defaults in the installers is the install path ‘to c:\Drupal Wamp’ and the mysql port from 3306 to 3307 – my server already has a mysql install on 3306 that i dont want to use. Platform Windows 7 Ultimate with all patches – this is my own local server for me to try 7 out. Any ideas? Tom |
|
|
Hi, It is strange, we can not reproduce it. Could you try to restart the servers? Could you check the mysql credentials in your_installdir/apps/drupal/htdocs/sites/default/settings.php? Could you try to login in the WAMP database using these credentials? |
|
|
Hi, Did as you requested – logged in using MySQL workbench as user bitnami with no problems. The DB connection specified looks good i.e. correct port etc – MySQL and APache are running and connect to phpMyAdmin with no problems (as administrator that is). Can see the drupal7 database has been created. Restart the services several times – same error when trying to access drupal. At a loss! Tom |
|
|
Could you try to specify “127.0.0.1” instead of “localhost” in the database configuration in the settings.php file? |
|
|
Hi, did as you suggest, and its still the same error – even says drupal@localhost but have i check 3 times i changed it to 127.0.0.1 as below $databases = array ( Tom |
|
|
Hi, The problem is the “unix_socket” line. Please remove it or download again the new Drupal 7 windows modules that it is fixed. Cheers, thanks for reporting it. |
|
|
Hi, just deleted the offending line and it worked fine. I did download the r01 release module and it still has the same problem (same offending line) as i reinstalled it all from scratch – in the end just deleted the line! :-) Thanks for the help TOm |
|
|
Hi, Thanks for trying it. We released a new fixed version. |

