My responder stopped working!!

[darellbee]

I have an autoresponder which has stopped working. I cannot tell whether a settings change has interferred or not. Before I start all over again, can you please tell me if anything has changed on your end. Is there a reason it has worked before and all of a sudden, it doesn't work anymore? This is the error message I am now receiving.

Warning: mysql_connect() [function.mysql-connect]: Access denied for user 'user'@'localhost' (using password: YES) in /home/myspace/public_html/responder/functions.php on line 93
Could not connect : Access denied for user 'user'@'localhost' (using password: YES)

Thanks for your help!!!

[Fearghal]

I have an autoresponder which has stopped working. I cannot tell whether a settings change has interferred or not. Before I start all over again, can you please tell me if anything has changed on your end. Is there a reason it has worked before and all of a sudden, it doesn't work anymore? This is the error message I am now receiving.

Warning: mysql_connect() [function.mysql-connect]: Access denied for user 'user'@'localhost' (using password: YES) in /home/myspace/public_html/responder/functions.php on line 93
Could not connect : Access denied for user 'user'@'localhost' (using password: YES)

Thanks for your help!!!

Im guessing you are being denied access to the Database?

Make sure everywhere it asks for your database password, the password is correct. For eg in SMF most maintenance settings require DB Authentication in each setting. If the pass is incorrect - you will be denied access.

Also - Make sure the DB credentials you are using have the required permissions. Just allow all privileges if you don't know which one you need.

EDIT - You should check the permissions for the responder script too.

Good Luck - Please post back or PM me if this does not work for further assistance :happysad:

[darellbee]

Fearghal, I appreciate your input. I wound up deleting the current user and creating a new one, and, thank goodness, it worked. I would have normally deleted the entire responder and starting over, but that would not have pin pointed the problem, so I was glad I did not have to go through all of those steps.

Anyway, the problem has been solved. Thanks again for your help!!

[Nathan H]

*thread closed issue solved*