Google Ads

Google Ads

Bible Wheel Book

Google Ads

+ Reply to Thread
Results 1 to 5 of 5
  1. #1
    Join Date
    Jun 2007
    Location
    Yakima, Wa
    Posts
    14,829

    Arrow MySQL - Connection Failed: [HY000] [MySQL][ODBC 3.51 Driver] Access denied for user

    I tried to use the MySQL ODBC 3.51 Connector. It failed with the message "Connection Failed: [HY000] [MySQL][ODBC 3.51 Driver]Access denied for user ..." I did all the usual debugging, such as checking connection settings to no avail. Then after about an hour searching the internet, I found the answer here:

    You might have an error message like this: "Connection Failed: [HY000] [MySQL][ODBC 3.51 Driver]Access denied for user ‘newaccount’@’192.168.11.1′ (using password: YES)“. The root causes of this error message are: you type wrong password, OR the password is too complex.

    MySQL ODBC 3.51 No-Complex Password

    Warning – You might have a serious headache with MySQL ODBC 3.51 if the password in your GRANT command contains special characters, such as ! @ # $ % ^ ?. MySQL ODBC 3.51 ODBC Driver does not support these special characters in the password box. The only error message you would receive is “Access denied” (using password: YES)
    I had a caret ^ in my password. An hour for a caret? Welcome to the wonderful world of software engineering.
    • Skepticism is the antiseptic of the mind.
    • Remember why we debate. We have nothing to lose but the errors we hold. Who but a stubborn fool would hold to errors once they have been exposed?

    Check out my blog site

  2. #2
    Unregistered Guest

    You are awesome

    Talk about finding a needle in a haystack. Who would have thought that a vendor would discourage/fail on a complex password. I spent a few hours trying to figure out why I couldn't connect with ODBC. We had a @ character in our password.

    Thanks for sharing and helping me solve my problem.

  3. #3
    Join Date
    Jun 2007
    Location
    Yakima, Wa
    Posts
    14,829
    Quote Originally Posted by Unregistered View Post
    Talk about finding a needle in a haystack. Who would have thought that a vendor would discourage/fail on a complex password. I spent a few hours trying to figure out why I couldn't connect with ODBC. We had a @ character in our password.

    Thanks for sharing and helping me solve my problem.
    Great! Thanks for letting me know it helped. I've benefited countless times by folks posting their solutions to obscure problems.
    • Skepticism is the antiseptic of the mind.
    • Remember why we debate. We have nothing to lose but the errors we hold. Who but a stubborn fool would hold to errors once they have been exposed?

    Check out my blog site

  4. #4
    Unregistered Guest

    Thank You

    Had an '#' in my password for the remote user, it allows me to have that password as the root user on the actual box

  5. #5
    Join Date
    Jun 2007
    Location
    Yakima, Wa
    Posts
    14,829
    Quote Originally Posted by Unregistered View Post
    Had an '#' in my password for the remote user, it allows me to have that password as the root user on the actual box
    Awesome! Glad to help. Software development would be impossible if folks didn't share their solutions online. The best site I've found for that is StackOverflow.com. I get answers there almost every day.
    • Skepticism is the antiseptic of the mind.
    • Remember why we debate. We have nothing to lose but the errors we hold. Who but a stubborn fool would hold to errors once they have been exposed?

    Check out my blog site

Thread Information

Users Browsing this Thread

There are currently 2 users browsing this thread. (0 members and 2 guests)

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may post replies
  • You may not post attachments
  • You may edit your posts
  •