Page 1 of 1
Unable to connect to db on windows
Posted: Wed Feb 20, 2008 11:14 am
by schrei5
Hi,
I just tried to install OpenEMM but got the following problem:
Code: Select all
Starting up .. home is c:\OpenEMM .. found codebase .. setup:
Setup database, please enter the super user password defined during MySQL instllation:
Enter password: ****
Database created, now setting up initial data, please enter again your databae super user password:
Enter password: ****
Database setup completed.
Failed to connect to database
[press return]
The openemm db and the tables have been created but the script is not able to connect to the database and it doesn't says why
Setup of OpenEMM for Windows
Posted: Wed Feb 20, 2008 10:23 pm
by maschoff
This article describes (in German) how to set up OpenEMM for Windows:
http://www.agnitas.de/pdf/OpenSource-407.pdf
Maybe it provides some helpful tips.
failed to connect to database
Posted: Thu Feb 21, 2008 2:26 pm
by blackeagle
hello,
i have the same problem. i have checked other articles in the openemm forum, but i cannot solve this problem.
so maybe anyone can help with this problem, please?
Posted: Thu Feb 21, 2008 4:44 pm
by maschoff
What version of OpenEMM do you use?
unable to connect
Posted: Thu Feb 21, 2008 5:20 pm
by blackeagle
hello,
I use the version 5.3., but I also tried the new version 5.4. both with the same result.
Posted: Thu Feb 21, 2008 5:30 pm
by maschoff
For version 5.4 try:
#mysql -u root -p
>GRANT DELETE, INSERT, UPDATE, LOCK TABLES, SELECT, ALTER, INDEX, CREATE TEMPORARY TABLES, DROP, CREATE ON openemm.* TO 'agnitas'@'localhost' IDENTIFIED BY 'openemm';
>FLUSH PRIVILEGES;
>quit
This creates user agnitas with the necessary permissions in case the user does not exist already. Does this work?
now it works
Posted: Thu Feb 21, 2008 8:24 pm
by blackeagle
hello,
Thanks. It works. I can´t believe it, but it is true! That´s it!!
thanks...
Posted: Fri Feb 22, 2008 8:18 am
by schrei5
...works for me too
Thanks!
Posted: Fri Feb 22, 2008 9:47 am
by maschoff
Great. I posted a bug report to our bugtracker on SourceForge and will make sure, that the problem ist fixed in RC2. Thanks for your feedback!