Bug #60076 Workbench looks for my.ini in the wrong directory
Submitted: 10 Feb 2011 7:11 Modified: 17 Jun 2011 19:08
Reporter: Jonathan Livni Email Updates:
Status: Closed Impact on me:
Category:MySQL Workbench Severity:S2 (Serious)
Version:5.2.31a OS:Microsoft Windows (Win7 64bit)
Assigned to: CPU Architecture:Any
Tags: configuration, directory, my.ini

[10 Feb 2011 7:11] Jonathan Livni
After installing MySQL Community Server 5.59 (64bit) and MySQL Workbench 5.2.31a and setting it up I try accessing the db's configuration and receive the following error:

Configuration file 'C:\Program Files\MySQL\MySQL Server 5.0\my.ini' can not be found. New file will be created on apply of changes.

I click OK. Then when trying to apply any change I get a second IO Error for not being able to write to the file.

It figures as my installation is at C:\Program Files\MySQL\MySQL Server 5.5 and not at C:\Program Files\MySQL\MySQL Server 5.5. But why does Workbench search there?

How to repeat:
This reporoduces for me every time, even if I uninstall-reinstall all MySQL products
[10 Feb 2011 7:17] Jonathan Livni
Two corrections to the text above:
1) I get the error while try to access the configuration via Workbench (if it wasn't clear)
2) My installation is at "... 5.5" instead of "... 5.0" where Workbench is looking
[18 Feb 2011 22:02] Alfredo Kojima
How did you create the server profile? If it was created with the wizard in 5.2.31, can you check the service definition for your server and check if the path to config file is correct? If not, you'll have to fix it and also fix the path in the Manage Server Instances dialog (access it from Home)
[19 Mar 2011 0:00] Bugs System
No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".
[17 Jun 2011 19:08] Paul DuBois
Noted in 5.2.34 changelog.

Workbench sometimes looked for my.ini in the wrong directory.