Hi
I have been stuck for awhille now on the database configuration page. If I enter in the wrong info, i get an error message. but if I enter the correct info i just get returned to the same page with the fields cleared. Np tables have been created and I never make it to the welcome page.
I read somewhere on here that I may need to grant permissions to my login. The login I am using is the database owner. Does that still apply?
I did try:
GRANT SELECT, INSERT, UPDATE, DELETE, CREATE, DROP, INDEX,
ALTER, CREATE TEMPORARY TABLES, LOCK TABLES
ON user_database_name
TO 'user_login'@'user_ipaddress'
IDENTIFIED BY 'user_password';
All that did was produce an error:
Notice: iconv(): Wrong charset, cannot convert from `CP1252' to `utf-8//TRANSLIT' in /var/www/phpmyadmin/libraries/database_interface.lib.php on line 152
Can someone please help me out.
thanks
Comments
I'm having the same problem
I'm having the same problem - DB configuration page just loops back to itself. Webhost swears my DB user has full permissions...anybody have any other ideas on what to try? Its hard to troubleshoot without error messages. :P
Try this...
OK, I don't know if this will always fix this issue, but it worked for me.
Because I was not getting an error when I entered the correct information, it was obvious that my site WAS at least talking to the database. So I went in and manually updated the /sites/default/settings.php file with my database information (find the line that starts with $db_url = 'mysql:// (on my code it was line 93) and replace the database name, login, and password values with your own information). I then uploaded the changed file and went to www.yoursitename.com/install.php and it said Drupal had been successfullly installed. It then allowed me to go on to the site and start configuring.
HTH someone!
It worked.
Thanks so much. This has been driving me nuts. That worked.
Installation stalls at install.php
The above manual alteration to the settings.php file sorted the problem for me too. Many thanks for this.
RE: Try This...
Thanks for posting this workaround, it helped me out as well!