FORUMS


The Form Tools forums are no longer active, but the old posts have been archived here. Please see the Help page on how to get help / report issues.

Thread Rating:
  • 1 Vote(s) - 5 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Installation database error
#1
I am installing FORMTOOLS on Mac OS x 10.6 and have run into a problem at Step 3 of the install process

The following error occurred:

Sorry, we were unable to connect to the database using the information you supplied. The error message the database returned is: No such file or directory

Please double-check your database settings and click the Continue button again.

I am running MySQL 5.5.15.

Could anyone help narrow down what file/directory this message may be referring to ?

Would appreciate any help

Thanks[/quote]
Reply
#2
Further to my post, the following info applies, which may be useful...

Database hostname localhost
Database name formtools
Database username guy
Database password (my password)
Database table prefix ft_

Checking further:

1. User 'guy' has all MySQL privileges except GRANT
2. MySQL folder 'formtools' is set to Read-Write for my OS X user
3. MySQL full version name is 'mysqlnd 5.0.7-dev - 091210 - $Revision: 304625 $' ...in Step 2 the installation script 'Failed' the version check and I overrode this. Is this a potential problem ?

Hope this helps...
Reply
#3
Hi guyd,

Unfortunately, there's not much I can help with for this problem: it just means that the info isn't correct... beyond double-checking all the database info you supplied, I don't know what else to suggest.

Quote:.in Step 2 the installation script 'Failed' the version check and I overrode this. Is this a potential problem ?

Nope! This occasionally happens if the MySQL identifier string returned isn't in a standard format, so the backend code doesn't know how to ascertain the major version number. But as long as you're running MySQL 4 or later, it's fine.

- Ben
Reply
#4
(Sep 9th, 2011, 9:10 AM)Ben Wrote: Hi guyd,

Unfortunately, there's not much I can help with for this problem: it just means that the info isn't correct... beyond double-checking all the database info you supplied, I don't know what else to suggest.

Quote:.in Step 2 the installation script 'Failed' the version check and I overrode this. Is this a potential problem ?

Nope! This occasionally happens if the MySQL identifier string returned isn't in a standard format, so the backend code doesn't know how to ascertain the major version number. But as long as you're running MySQL 4 or later, it's fine.

- Ben

Thanks Ben.

FORM TOOLS looks like it will do what I want so I'll spend a bit more time to re-check and do some testing.

I guess it's possible that this may be a permissions problem somewhere along the line. Do you have any experiences with installing FORM TOOLS on OS X and file/folder permission issues with MySQL ?

Guy
Reply
#5
Hey Guy,

Yeah, I run it locally with MAMP quite a bit - but permissions have never been a problem (no config necessary: go Mac!). Database-wise, the default settings are username=root, password=root, and that's it... I rarely delve into configuring MySQL for additional users (only for testing now and then). So I'm afraid I'm not going to be much help, sorry about that. :-(

Anyway, good luck! If you find anything out, do post back if it can help other people.

- Ben
Reply
#6
Wink 
SOLUTION FOUND:

I had the exact same problem on a mac, it is a problem with the mysql setup/combined with php..

tried to connect using the methods listed here
http://www.w3schools.com/php/php_mysql_connect.asp
PHP Code:
<?php
// Create connection
$con=mysqli_connect("example.com","peter","abc123","my_db");

// Check connection
if (mysqli_connect_errno($con))
  {
  echo 
"Failed to connect to MySQL: " mysqli_connect_error();
  }
?>

which gave me the exact same error as the installer

a quick google gave me this solution
http://stackoverflow.com/questions/42199...connect-vi

essentially the fix is creating a symbolic link
For some reason mysql on OS X gets the locations of the required socket file a bit wrong, but thanks to a veritable wizard I know (that's you, Gavin) the solution is as simple as setting up a symbolic link.

You may have a socket (appearing as a zero length file) as /tmp/mysql.sock or /var/mysql/mysql.sock but 1 or more apps is looking in the other location for it.

Rather than move the socket and have to edit config files and remember to keep edited files local and away from servers where the paths are correct, simply create a symbolic link so your mac finds the required socket, even when it's looking in the wrong place!

If you have /tmp/mysql.sock but no /var/mysql/mysql.sock then...

cd /var
mkdir mysql
cd mysql
ln -s /tmp/mysql.sock mysql.sock

have fun ... and great product "form tools" impressed
Reply
#7
Awesome! Thanks.
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)