Installation on server
Sun, 27/12/2009 - 03:28
Hi, I am new to ProsePoint and am a real novice when it comes to server side stuff. I haven't been able to find instructions for installing ProsePoint on a hosted server. I uploaded the downloaded ProsePoint files to the root folder (www.wadiocese.com/prosepoint), changed the default/defaultsetting file to default/setting.php, changed permissions to 777 and then typed in the url. The ProsePoint configuration box appeared and I got to the database configuration part. Here I got stuck. I had prevoiously set-up a new database (prosepoint), user (prosept) and password on my host server, but it seems whatever combinations I enter, there is a connection errpr (Failed to connect to your MySQL database server. MySQL reports the following message: Access denied for user 'prosept'@'localhost' (using password: YES).). I've tried to add my server "prefix": wadioce_prosepoint to all the entried, to the database name and user, but not password and it fails each time. Any Advice?
Thanks. Peter
Sun, 27/12/2009 - 03:38
#1
Offline
Slightly different message
I git a slightly different message when attempting to configure the Database Configuration: Failed to select your database on your MySQL database server, which means the connection username and password are valid, but there is a problem accessing your data. MySQL reports the following message: Access denied for user 'wadioce_prosept'@'localhost' to database 'prosepoint'.
Wed, 30/12/2009 - 10:53
#2
...
Hi,
> changed the default/defaultsetting file to default/setting.php,
Actually, you should have copied .../sites/default/default.settings.php to a new file called .../sites/default/settings.php. You may have already done this correctly, and it's just a typo in your post.
> I had prevoiously set-up a new database (prosepoint), user (prosept) and password on my host server,
Sounds fine so far. Using this as an example, the database is prosepoint, the user is prosept, and the password is whatever you chose.
For most common server setups, I don't think you need to add any prefixes to your database name, but this really depends on your server and how it's configured.
Overall, this sounds very much like a database access permissions issue ie. incorrect username, password or database.
I'd suggest you talk to your hosting provider and confirm that the credentials of the database attached to your account is actually what you think it is.