Install -error-

Trouble during PacsOne Server installations
Post Reply
tuxbully
Posts:9
Joined:Mon Nov 01, 2004 3:21 pm
Install -error-

Post by tuxbully » Mon Nov 01, 2004 4:14 pm

I am currenlty running MySQL 4.1.7, PHP 5.0.2 and Apache 2.0.52 on Windows XP SP2. I am trying to install PacsOne Server Premium Edition 1.1.9 and can not get passed the following error <screenshot attached >
Image

Thank You :wink:

pacsone
Site Admin
Posts:3149
Joined:Tue Sep 30, 2003 2:47 am

Post by pacsone » Mon Nov 01, 2004 5:16 pm

It looks like the default path for the latest MySql release (4.1.x) has changed again. There're 2 workarounds for this:

1. Download and install the last MySql 4.0.x release instead of the 4.1.x release.

2. Modify the MySql registry setting:

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Mysql\ImagePath

and delete the "-default-files" parameter, i.e., leave only the full path with no parameters:

C:\Program Files\MySQK\MySQL Server 4.1\bin\mysqld-nt

and then run the Setup.exe program again under the directory where PacsOne Server is installed.

You may want to save the MySQL parameters information first in case you need it later.

tuxbully
Posts:9
Joined:Mon Nov 01, 2004 3:21 pm

RE

Post by tuxbully » Mon Nov 01, 2004 6:52 pm

Thank You for the Quick Reply - :D
I looked @ the reg key for the Image path and it is as follows >

"C:\Program Files\MySQL\MySQL Server 4.1\bin\mysqld-nt" --defaults-file="C:\Program Files\MySQL\MySQL Server 4.1\my.ini" MySQL

I tried changing this line a couple different ways and when I do the service fails to start. I must be setting it incorrectly or something ..... Can You please tell me exactly what it should read.
Thanks

pacsone
Site Admin
Posts:3149
Joined:Tue Sep 30, 2003 2:47 am

Post by pacsone » Mon Nov 01, 2004 7:04 pm

You can try this:

1. Changing the registry ImagePath setting to remove the default parameter, i.e., set it to:

C:\Program Files\MySQL\MySQL Server 4.1\bin\mysqld-nt

2. Copy the my.ini under C:\Program Files\MySQL\MySQL Server 4.1\my.ini to your Windows directory, e.g., for WinXP, copy it to C:\Windows

and see if you can start MySql with the above modifications.

tuxbully
Posts:9
Joined:Mon Nov 01, 2004 3:21 pm

RE

Post by tuxbully » Mon Nov 01, 2004 7:18 pm

Thanks that worked :D :D However, now i got a new error during the install.
See Attached >
Image

pacsone
Site Admin
Posts:3149
Joined:Tue Sep 30, 2003 2:47 am

Post by pacsone » Mon Nov 01, 2004 7:57 pm

There's an extra quote character (") in the ImagePath registry setting.

Try removing the extra quote character and then run Setup.exe again.

tuxbully
Posts:9
Joined:Mon Nov 01, 2004 3:21 pm

RE

Post by tuxbully » Mon Nov 01, 2004 8:21 pm

Your Are correct :arrow: Thanks Again :D :D
Excuse me for being a n00b .... Windows is not my bag :evil: :evil: a Linux version would be nice 8) and a lot more robust and easier.

Note: I had to change one other thing for it to work with my version of MySQL.

mysql> SET PASSWORD FOR
-> 'some_user'@'some_host' = OLD_PASSWORD('newpwd');

and this is because MySQL 4.1 and up uses an authentication protocol based on a password hashing algorithm that is incompatible with that used by older clients. If you upgrade the server to 4.1, attempts to connect to it with an older client may fail.

You need to do this for every user or change the default behavior.

pacsone
Site Admin
Posts:3149
Joined:Tue Sep 30, 2003 2:47 am

Post by pacsone » Mon Nov 01, 2004 9:13 pm

This is good information to know about, and maybe it's time for PacsOne to switch to the latest MySql client libraries.

On a side note, the Linux version of PacsOne Server is coming soon, hopefully before the end of this year.

Jonathan
Posts:184
Joined:Mon Mar 22, 2004 11:52 am
Location:The Netherlands
Contact:

MySQL password hashing algorithm

Post by Jonathan » Fri Nov 05, 2004 9:48 am

See for deails this message with links to the MySQL site.

http://pacsone.net/forum/viewtopic.php?p=593#593

A solution is to make new passwords for active users on the new 4.1 MySQL installation. The passwords should be in the correct hashing format because they are generated with the new hashing algorithm.

Jonathan

Post Reply