Bug #42397 | Upgrading from setup.exe install to a .msi install is not recognized | ||
---|---|---|---|
Submitted: | 27 Jan 2009 23:02 | Modified: | 9 Feb 2009 18:00 |
Reporter: | Patrick Crews | Email Updates: | |
Status: | Duplicate | Impact on me: | |
Category: | MySQL Server: Config Wizard | Severity: | S3 (Non-critical) |
Version: | 5.0+ | OS: | Windows |
Assigned to: | Assigned Account | CPU Architecture: | Any |
Tags: | install, msi, setup.exe, upgrade, vista, windows |
[27 Jan 2009 23:02]
Patrick Crews
[5 Feb 2009 22:40]
Iggy Galarza
I tested upgrading from the mysql-5.1.29 available on dev.mysql.com and a 5.1.31-essential installer package created with the changes for Bug#4217 on Windows XP and Vista (32-bit) and was unable to reproduce the problem. This bug should be fixed in 5.1.32 so I'll mark it re-test to make sure bug reporter has same experience.
[9 Feb 2009 18:00]
Patrick Crews
This behavior appears to be a symptom of: Bug #4217 Multiple Uninstallation Entries in Add/Remove Programs Tests with a .msi installer incorporating this bug fix could not repeat the problem. Expect 5.1.32's .msi files to not have this issue.
[23 Feb 2009 20:41]
Lars Heill
Tried on Vista x64: 1. installed mysql-5.1.30-winx64.zip/setup.exe 2. set password, started server 3. installed mysql-5.1.32-winx64.msi 4. configuration complained about pid in use 5. pressed "Ignore" (twice) 6. set new password 7. confirmed server running with new pid 8. connect with new password succeeded 9. uninstall with mysql-5.1.32-winx64.msi 10. uninstall complained, shut down process (the new pid) 11. uninstall complained, file (old pid) in use 12. pressed "Retry" 13. uninstall completed, service removed, MySQL/MySQL Server 5.1/bin dir remains (empty), my.ini remains, my <timestamp>.ini.bak remains.