Error msg when installing PacsOne... MySQL client upgrade??

[Antw1]

After installing an setting up MySQL 4.1.7, I keep getting the following error message when installing PacsOne Standard:

Error configuring MysQL database: DB_NAME
MySQL Error: Client does not support authentication protocol requested by server; consider upgrading MySQL client.
Please verify the specified MySQL Username and password are valid.

I get the same message trying to install on 2 different machines (WinXP Pro and WinServer 2003).
Anybody has some insight about that upgrade?
Thanks.

[Jonathan]

A few questions:

1 - Is this an upgrade or a fresh installation?
2 - What is the name of your database? Is is called 'DB_NAME'?
3 - What account are you using to log in?
4 - Are you able to log in at the mysql command line tool? (change to bin directory in the directory where mysql is installed and enter the following statement: mysql -u [username] -p, replace [username] with the username you use to log in, normally root.)

It might be due to the following reason (found in the MySQL manual also available on their site). In the process of improvement MySQL has changed the password hash algorithm, the new algorithm seems to be in use since version 4.1.1. See their site for details:

From section A: Problems and Common Errors
A.2.3 Client does not support authentication protocol (http://dev.mysql.com/doc/mysql/en/Old_client.html)

From section 5:
5.5.9 Password Hashing in MySQL 4.1 (http://dev.mysql.com/doc/mysql/en/Password_hashing.html)
5.5.9.1 Implications of Password Hashing Changes for Application Programs (http://dev.mysql.com/doc/mysql/en/Appli ... d_use.html)

Maybe this has something ot do with the problem as well.

Jonathan

[Antw1]

It is a fresh install. Now, I've tried on 3 machines (WinXP Pro, Win 2003 Server, Win2000 Pro) with the exact same error msg.

My database name is "archive".

I'm using the account I created using the PacsOne guidelines:
mysql>grant all privileges on archive.* to USER_NAME@localhost identified by 'PWD';
(USER_NAME and PWD being my name and my phony password...)

I'm able to login with the statement you suggested. Also, I usually use the MySQL Client command prompt provided with MySQL 4.1.7, but it works just as well with navigating to the \bin directory...

Thanks Jonathan. I will look into the topics you suggested.

[Antw1]

Dead on with the updated pwd hashing !
Alright now the real work begins...
Thanks a million Mr J. !

[pacsone]

Yes, Jonathan deserves a round of applause here

[Jonathan]

It might be due to the following reason (found in the MySQL manual also available on their site). In the process of improvement MySQL has changed the password hash algorithm, the new algorithm seems to be in use since version 4.1.1. See their site for details:

From section A: Problems and Common Errors
A.2.3 Client does not support authentication protocol (http://dev.mysql.com/doc/mysql/en/Old_client.html)

From section 5:
5.5.9 Password Hashing in MySQL 4.1 (http://dev.mysql.com/doc/mysql/en/Password_hashing.html)
5.5.9.1 Implications of Password Hashing Changes for Application Programs (http://dev.mysql.com/doc/mysql/en/Appli ... d_use.html)

Maybe this has something ot do with the problem as well.

Jonathan

There are two solutions:

1 - Generate new passwords with the new password hashing algorithm, this solves the problem for the future as well.

2 - The other option, which in my opinion is depricated, is to start the MySQL with the option --old-password option. This causes passwords to be created with the old encryption even if you are creating new passwords (backward compatibility).

The problem with this might be that in newer releases this option will be abandoned and you still have to make new passwords. (IMHO this solves the need for staying on a MySQL version lower than 4.1 as stated on the download page, as this is the only reason for that I believe. Keep in mind that I have not tested this.)

More details are in the folowing section:
5.5.9 Password Hashing in MySQL 4.1 (http://dev.mysql.com/doc/mysql/en/Password_hashing.html)

Jonathan

[pacsone]

I've posted a note in the PacsOne download page about this issue and ask users not to install MySql 4.1.x for the time being until we find a solution that is compatible for all MySql releases.

The upcoming PacsOne Server Premium Edition 2.1.2 will take care of this issue by supporting all MySql releases (it will require users to install the MYSQLI PHP extension if MySql 4.1.x is installed, or the regular MYSQL PHP extension for MySql releases prior to 4.1.x).

So until PacsOne Server Premium Edition 2.1.2 is released, please install the latest MySql 4.0.x release instead.