Description:
I just upgraded from MySQL 4.0.20d to 4.1.8 running on Windows XP Pro. Since the previous installed version was 4.0.20d, instructions indicated this required an unistall and reinstall. I ran into an interaction between my software firewall and the MySQL Server Instance Configuration Wizard resulted in the MySQL Wizard failing. By making educated guesses, based on my several decades of software development experience, I was able to get things working again. But I doubt that a normal user would have known what to do.
How to repeat:
Here is the complete list of steps I followed to do the upgrade:
1) I dumped the database with the command:
mysqldump --opt --all-databases --result-file=all_databases_20050111.sql --verbose -uroot -p
2) I shut down the MySQL server:
My Computer>Manage>Services and Applications>Services>MySQL>Properties>General
Click on "Stop"
Change Startup type to "disabled" and click on "Apply"
3) I removed the MySQL service with the command:
mysqld --remove
4) I uninstalled MySQL 4.0.20d by clicking on:
Start>Settings>Control Panel>Add or Remove Programs>MySQL>Remove
5) I unpacked mysql-4.1.8-win.zip which produced Setup.exe
6) I double-clicked on Setup.exe and followed the installation procedure. I selected "Custom" installation, and instructed it to install everything except the MySQL config utility for DOS-derived versions of Windows. I also changed installation partition from C: to D:.
7) At the end of the installation, the MySQL Server Instance Configuration Wizard automatically ran. I made my selections and clicked on "Execute". The "Prepare Configuration" and "Write Configuration File" steps went fine, but at the "Start Service" step, the Zone Alarm software firewall displayed a dialog box asking whether I wanted to allow some MySQL component (I forgot to copy down the name) to access the network. This is normal behavior for Zone Alarm, whenever it encounters an executable it hasn't seen before. All other applications I've dealt with will block at this point. If I tell Zone Alarm to permit the network access, these other applications then resume and behave normally. However the MySQL Server Instance Configuration Wizard didn't block. Instead, before I had a chance to tell Zone Alarm to allow the MySQL Wizard to access the network, the Wizard continued as if access had been denied, and marked its "Apply Security Settings" step as having failed. At this point, rerunning the MySQL Server Instance Configuration Wizard failed. I made an educated guess that the Wizard probably does three things: a) create a my.ini file, b) install Mysql as a Windows service, and c) add the path to the executable to the system's PATH environment variable. To manually undo these, I did the following:
a) I removed d:/Program Files/MySQL/MySQL Server 4.1/my.ini
b) I ran 'mysqld --remove'
c) I went to My Computer>Properties>Advanced>Environment Variables>System Variables>Path>Edit, and removed "D:\Program Files\MySQL\MySQL Server 4.1\bin" from the path.
I was then able to rerun the MySQL Server Instance Configuration Wizard and it reported that it successfully completed all 4 of its steps.
Description: I just upgraded from MySQL 4.0.20d to 4.1.8 running on Windows XP Pro. Since the previous installed version was 4.0.20d, instructions indicated this required an unistall and reinstall. I ran into an interaction between my software firewall and the MySQL Server Instance Configuration Wizard resulted in the MySQL Wizard failing. By making educated guesses, based on my several decades of software development experience, I was able to get things working again. But I doubt that a normal user would have known what to do. How to repeat: Here is the complete list of steps I followed to do the upgrade: 1) I dumped the database with the command: mysqldump --opt --all-databases --result-file=all_databases_20050111.sql --verbose -uroot -p 2) I shut down the MySQL server: My Computer>Manage>Services and Applications>Services>MySQL>Properties>General Click on "Stop" Change Startup type to "disabled" and click on "Apply" 3) I removed the MySQL service with the command: mysqld --remove 4) I uninstalled MySQL 4.0.20d by clicking on: Start>Settings>Control Panel>Add or Remove Programs>MySQL>Remove 5) I unpacked mysql-4.1.8-win.zip which produced Setup.exe 6) I double-clicked on Setup.exe and followed the installation procedure. I selected "Custom" installation, and instructed it to install everything except the MySQL config utility for DOS-derived versions of Windows. I also changed installation partition from C: to D:. 7) At the end of the installation, the MySQL Server Instance Configuration Wizard automatically ran. I made my selections and clicked on "Execute". The "Prepare Configuration" and "Write Configuration File" steps went fine, but at the "Start Service" step, the Zone Alarm software firewall displayed a dialog box asking whether I wanted to allow some MySQL component (I forgot to copy down the name) to access the network. This is normal behavior for Zone Alarm, whenever it encounters an executable it hasn't seen before. All other applications I've dealt with will block at this point. If I tell Zone Alarm to permit the network access, these other applications then resume and behave normally. However the MySQL Server Instance Configuration Wizard didn't block. Instead, before I had a chance to tell Zone Alarm to allow the MySQL Wizard to access the network, the Wizard continued as if access had been denied, and marked its "Apply Security Settings" step as having failed. At this point, rerunning the MySQL Server Instance Configuration Wizard failed. I made an educated guess that the Wizard probably does three things: a) create a my.ini file, b) install Mysql as a Windows service, and c) add the path to the executable to the system's PATH environment variable. To manually undo these, I did the following: a) I removed d:/Program Files/MySQL/MySQL Server 4.1/my.ini b) I ran 'mysqld --remove' c) I went to My Computer>Properties>Advanced>Environment Variables>System Variables>Path>Edit, and removed "D:\Program Files\MySQL\MySQL Server 4.1\bin" from the path. I was then able to rerun the MySQL Server Instance Configuration Wizard and it reported that it successfully completed all 4 of its steps.