MySQL ODBC 3.51 Driver, odbc3.51

MySQL ODBC 3.51 Driver, odbc3.51

MySQL ODBC 3.51 Driver-Access Denied

 

When a colleague reported that MySQL ODBC 3.51 Drive was configured on the application server, the following error was reported during the connection test:

 

 

ERROR [HYT00] [MySQL] [ODBC 3.51 Driver] Access denied for user: 'xxx @ xxxx' (Using password: YES)

 

 

This error may occur in multiple situations:

 

 

 

1: The account password is incorrect or the account does not exist.

 

 

If the account password is incorrect or does not exist, the ERROR [HYT00] [MySQL] [ODBC 3.51 Driver] Access denied for user: 'xxx @ xxxx' (Using password: YES) will be reported.

 

 

2: The account password has special characters, such as special characters! @ # $ % ^ ?, This error may also occur.

 

 

Create a test account. The password contains a special character!

mysql> grant select on MyDB.* to test@'%' identified by 'Ac3435!6p';

Query OK, 0 rows affected (0.00 sec)

mysql> flush privileges;

Query OK, 0 rows affected (0.00 sec)

 

 

This error occurs when MySQL ODBC is configured on the test server. As shown below,

 

 

 

 

 

 

 

After searching, I found that MySQL ODBC 3.51 does not allow complex passwords, as shown in the following English documents. However, I downloaded and installed MySQL ODBC 5.3 to test that this version is completely usable. Of course, it is unclear from that version that complicated passwords have been supported. This tough feature is really amazing!

 

 

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! @ # $ % ^ ?. MySQL ODBC 3.51 ODBC Driver does not support these special characters in the password box. The only error message you wowould receive is "Access denied" (using password: YES)

 

 

 

 

In addition, if the network is disconnected, the port is disconnected, or the MySQL service is not enabled, the error "Can't connect to MySQL server on 'xxxxxx' (10060)" is reported.