Bug #53607 All server configuration lost on upgrade to Workbench 5.2.21 RC
Submitted: 12 May 2010 18:23 Modified: 19 May 2010 7:02
Reporter: Dave Nechodom Email Updates:
Status: Not a Bug Impact on me:
None 
Category:MySQL Workbench: Administration Severity:S3 (Non-critical)
Version:5.2.21 RC OS:Windows (XP Pro SP3)
Assigned to: CPU Architecture:Any
Tags: configuration, upgrade

[12 May 2010 18:23] Dave Nechodom
Description:
All server instance configuration data lost when upgrading from Workbench 5.2.20 Beta to 5.2.21 RC. Connection names revert to instance names.

How to repeat:
Configuration for several Linux-based server instances was customized using WB5.2.20. Connection names included Local50 (Windows), NAMain50 (RHEL3), NASmall50 (RHEL3). I uninstalled WB5.2.20, then installed the new WB5.2.21 RC. When I started the application, I found all the connection names changed to the value of the corresponding instance name and all the instance configuration settings reverted to the default values.

Suggested fix:
Don't delete configuration data when uninstalling the Beta. Import the configuration data completely & accurately in the RC.
[12 May 2010 18:50] MySQL Verification Team
Thank you for the bug report. How you did the upgrade? Removing the older version with Windows Control Panel or just running the install of new version? ( I did the last one without to lost the data you mentioned). Thanks in advance.
[12 May 2010 19:07] Dave Nechodom
When I've done upgrades in the past, I've been instructed to remove the existing installation when I tried to overwrite it with a new release. So, for the last four versions, I've uninstalled the existing version using 'msiexec -x ...', then installed the new version using 'msiexec -i ...'.
[19 May 2010 7:02] Susanne Ebrecht
Many thanks for writing a bug report. This is not a bug at all. You removed by accident the configure files by removing the old version.