Bug #12219 | mysqld-nt.exe usage verses mysqld-max-nt.exe usage during WinXP MSI Install | ||
---|---|---|---|
Submitted: | 27 Jul 2005 17:33 | Modified: | 30 Aug 2005 15:57 |
Reporter: | Darlene Bolko | Email Updates: | |
Status: | Not a Bug | Impact on me: | |
Category: | MySQL Server: Installing | Severity: | S3 (Non-critical) |
Version: | 5.0.7b | OS: | Windows (Windows XP [32bit)) |
Assigned to: | CPU Architecture: | Any |
[27 Jul 2005 17:33]
Darlene Bolko
[27 Jul 2005 19:46]
MySQL Verification Team
I tested this issue with a newest server 5.0.XX and I recommend you to do too. However I was unable to repeat the issue you reported or I missed something from you. Below what I did: - Installed the package with the installer and mysql-nt.exe was installed and started. - Launched MySQL Administrator. - Stopped the service with Service Control -> Start/Stop service - Then in Configure Service -> Path To Binary selected: E:\TestInstall\bin\mysqld-max-nt using the ... button at right side. - Applied the changes and below the successful log: Trying to stop the server ... Server was stopped. Trying to start the server ... Could not re-connect to the MySQL Server. Server was started. Done by MySQL Administrator.
[30 Aug 2005 15:57]
Valeriy Kravchuk
Thank you for taking the time to report a problem. Unfortunately you are not using a current version of the product your reported a problem with -- the problem might already be fixed. Please download a new version from http://www.mysql.com/downloads/ If you are able to reproduce the bug with one of the latest versions, please change the version on this bug report to the version you tested and change the status back to "Open". Again, thank you for your continued support of MySQL. Additional info: I've just reinstalled latest 5.0.11 several times on different XP machines (in a manner very close to those you described), and I have mysqld-max-nt.exe in the bin subdirectory of the installation directory I selected.