Bug #50563 Server instance configuration cannot find "my.ini"
Submitted: 23 Jan 2010 2:45 Modified: 15 Aug 2012 4:38
Reporter: Steve Miller Email Updates:
Status: No Feedback Impact on me:
None 
Category:MySQL Workbench Severity:S2 (Serious)
Version:5.2.14, 5.2.29 OS:Microsoft Windows
Assigned to: Assigned Account
Tags: cannot find, configuration, my.ini, server instance

[23 Jan 2010 2:45] Steve Miller
Description:
When configuring a new server instance from my client machine, MySQL workbench states that it cannot find the file "my.ini" at "%ProgramFiles%\MySQL\MySQL Server 5.1\my.ini".  I have checked that the file does indeed exist at this location on the server.

Setup Details:
Client: Windows XP SP3, 32 bit
Server: Windows Server 2003 Standard, 32 bit
MySQL Version: 5.1.42
MySQL Installation path: C:\Program Files\MySQL

How to repeat:
1. Click "New Server Instance"
2. Choose "Remote host" and provide the address of the remote server
3. Choose "Windows (MySQL 5.1 x86 Installer Package)"
4. Uncheck "Enable SSH login based administration"
5. Open connection manager and configure a connection to the remote server
6. Test the database connection (mine passes)
7. Use the default "%ProgramFiles%\MySQL\MySQL Server 5.1\my.ini" as the path, and "mysqld" as the configuration file section.

After clicking "Check path" or "Check section", MySQL Workbench reports that "The config file could not be found" and "The config file section is incorrect"
[25 Jan 2010 22:55] Miguel Solorzano
Thank you for the bug report.

"How to repeat:
1. Click "New Server Instance"
2. Choose "Remote host" and provide the address of the remote server"

Which server version is your remote host and OS version?. Thanks in advance.
[26 Jan 2010 0:45] Steve Miller
"Which server version is your remote host and OS version?. Thanks in advance."

Remote Server OS: Windows Server 2003 Standard
Remote Server DB ver: MySQL 5.1.42-community

I also experienced this issue with MySQL 5.0.67-community-nt
[28 Jan 2010 21:58] Robert Doucette
The reason the file "my.ini" cannot be found, even though it exists is because the default path provided is incorrect.  The default path should be "C:\Program Files\MySQL\MySQL Server 5.1\my.ini".  Notice the space between "Program Files".
[29 Jan 2010 0:21] Steve Miller
I have tried the following paths to the "my.ini" file (which does exist in this location), and have received the same result of "The config file could not be found" for each.

C:\Program Files\MySQL\MySQL Server 5.1\my.ini
"C:\Program Files\MySQL\MySQL Server 5.1\my.ini"
%ProgramFiles%\MySQL\MySQL Server 5.1\my.ini
\\<hostname>\c$\Program Files\MySQL\MySQL Server 5.1\my.ini
[29 Jan 2010 12:15] Maksym Yehorov
SSH access must be enabled in order to access to certain parts of Administrator module. One of the parts is config file management. Remote Windows needs also sftp access to fetch/upload config files. So if ssh server is installed, which support sftp, then the config path setting in Workbench should contain sftp's path. For example if sftp is set up with ftp's root dir at C: and config file is at C:\Program Files\MySQL\MySQL Server 5.1\my.ini so the ftp path to put to the workbench settings is /Program Files/MySQL/MySQL Server 5.1/my.ini.
We are working on remote file selector dialog which will help in locating remote files.
[1 Feb 2010 14:41] Johannes Taxacher
Steve,could you please check the problem again according to last comment from Maksym?
[3 Feb 2010 8:40] Tanel Abel
I checked where WB is trying to find my.ini file and somehow it tries to find it like this:
"C:\Program files\MySQL Workbench 5.2 OSS\%ProgramFiles%\MySQL\MySQL Server 5.1\my.ini"
[10 Feb 2010 16:49] Louis Breda van
Hello,

I have the same problem over here, using 64 bit server 5.5. Editing the xml and saving it as Windows_(MySQL_5.5_x64_Installer_Package).xml does not help.

Sincerely,

Louis
[2 Mar 2010 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".
[18 Mar 2010 16:40] Sydney Lee
2010-03-18

I have the same problem creating a new instance using workbench 5.2.15 OSS Beta and Mysql 5.0.51b-community-nt on Windows 32bit.

Workbench indicates it cannot find the following my.ini which exist
%ProgramFiles%\MySQL\MySQL Server 5.0\my.ini

echo %ProgramFiles% gives C:\Program Files
[31 Mar 2010 14:43] Mattias Andersson
2010-03-31

I can reproduce this problem too with WB 5.2.15 OSS.
[4 Sep 2010 12:47] Stefano Giraldo
I have the same problem on MySQL WorkBench 5.2.26 on Mac OSX 10.6.4.
The path the software is testing is: "C:\Documents and Settings\Administrator\%Program
  Files%\MySQL\MySQL Server 5.0\my.ini"
that't is obviously wrong.

Any idea when it will be fixed?

Thanx
[25 Oct 2010 15:53] Cesar Cesar
Apart from other reasons, it's due to configuration file section field. If you open the every file, the value inside its mysqld, when if you open my.ini file the section name its [mysql].
Typing only mysql is enough.
[9 Nov 2010 20:01] Bernhard Blaette
Here is what helped me to set the my.ini file in the Workbench 5.2.29 CE when creating a brand new Server Instance for MySQL 5.1 (I work on Windows 7):

- Click on "New Server Instance" as usual.
- I configured "localhost"
- set the "Database Connection" to work
- ignored the error "Check MySQL configuration file... File  doesn't exist"
- proceeded to "Review Parameters" and checked that tickbox "Change Parameters"!!
- "Next" took me to the page to set the "Path to Configuration File"
  there I entered "C:\Program Files\MySQL\MySQL Server 5.1\my.ini"
  and for "Server Instance" I entered the section in the my.ini "mysqld"
- "Next" on to the very end and the Workbench set up the Server Instance 

I will probably not be able to answer further questions, but this is what worked for me and I hope it will be useful to some of you too.
[1 Dec 2010 11:26] Eric Fernandez
I had the same issue, and fixed it with the same method than described by Bernhard. Still a bug though.
[25 Jan 2011 22:09] Felipe Castro
I had a similar issue although not exactly the same.
Initially, I installed MySQL 5.5 but later uninstalled to installed 5.1.  When trying to edit the configuration file in Workbench it was looking for it in the 5.5 location.
I fixed that by going to "Manage Server Instances -> System Profile" and correcting the "Configuration File" entry.
[24 May 2011 23:37] Miguel Solorzano
Could you please try version 5.2.33. Thanks.
[25 Jun 2011 23: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".