CiviCRM Community Forums (archive)

FINALLY GOT IT WORKING!!!!!!

I tried a fresh install from files unpacked on the server (finally figured out how to do that) and the installer ran to completion.  The completion page featured the message:

CiviCRM component files have been UPGRADED succesfully.
Please run the CiviCRM Database Upgrade Utility now. This utility will check your database and perform any needed upgrades.

BUT, when I tried to run the "upgrade utility" as requested, I still get the following error:

DB_DataObject Error: DB Error: connect failed

::sigh:: 

I tried running the civicrm component, and got the same error.  But after editing civicrm.settings.php under administration and under components, with the tcp() syntax added to the DSN, the component now runs. 

But the upgrade utility still doesn't run.  I'm concerned that I won't be able to upgrade this install.  I'll poke around some more...

Interestingly, I had to re-install after a botched database import, and was not able to get it to re-install, except by replacing every instance of CIVICRM_DSN in the installer files with the known good string that included the "tcp()" syntax.  So, I essentially hard-wired the database access string into the installer.  I think there were three different files where I had to make the substitution.

Let me know if you want more detail.

your best bet might be to hire someone from http://civicrm.org/professional/

lobo

I know it's been a long time since I replied to this topic, but I think an update is in order, as I ran into the SAME problem installing CiviCRM under Drupal on the same server.

Here's the fix:

in  ...modules/civicrm/install/civicrm.php

Replace

    $dsn = "mysql://{$config['mysql']['username']}:{$config['mysql']['password']}@{$config['mysql']['server']}/{$config['mysql']['database']}?new_link=true";

with

    $dsn = "mysql://{$config['mysql']['username']}:{$config['mysql']['password']}@tcp({$config['mysql']['server']})/{$config['mysql']['database']}?new_link=true";

Note the addition of "tcp(...)" encapsulating the server string.  This seemed necessary because my server required the string "localhost:/tmp/mysql5.sock" to access mysql.

Hope this helps somebody else....