Bug #71241 'Server/Options file' is looking at wrong directory
Submitted: 28 Dec 2013 9:39 Modified: 20 Sep 2014 9:47
Reporter: Luuk V Email Updates:
Status: Verified Impact on me:
None 
Category:MySQL Workbench: Administration Severity:S3 (Non-critical)
Version:6.0.8 OS:Windows (7)
Assigned to: CPU Architecture:Any
Tags: my.ini, options file

[28 Dec 2013 9:39] Luuk V
Description:
After opening the workbench, and going to Server/Options file i get the error:
09:57:40 [ERR][wb_admin_control.pyc]: Could not open the file "C:\Program Files\MySQL\MySQL Server 5.5\my.ini": 'NoneType' object has no attribute 'get_file_content'Created SQL connection to MySQL server. Server version is (5, 6, 15), conn status = True, active plugins = ['partition', 'sha256_password', 'INNODB_CMPMEM_RESET', 'INNODB_SYS_FIELDS', 'INNODB_BUFFER_POOL_STATS', 'CSV', 'mysql_native_password', 'INNODB_SYS_TABLES', 'INNODB_FT_BEING_DELETED', 'INNODB_BUFFER_PAGE', 'INNODB_CMP_PER_INDEX_RESET', 'PERFORMANCE_SCHEMA', 'ARCHIVE', 'INNODB_FT_INDEX_CACHE', 'INNODB_CMP', 'INNODB_SYS_FOREIGN_COLS', 'INNODB_FT_CONFIG', 'InnoDB', 'INNODB_FT_DEFAULT_STOPWORD', 'INNODB_TRX', 'binlog', 'INNODB_LOCKS', 'INNODB_CMPMEM', 'INNODB_SYS_DATAFILES', 'INNODB_FT_INDEX_TABLE', 'INNODB_LOCK_WAITS', 'MEMORY', 'INNODB_SYS_TABLESPACES', 'INNODB_METRICS', 'INNODB_SYS_INDEXES', 'MRG_MYISAM', 'INNODB_CMP_PER_INDEX', 'mysql_old_password', 'INNODB_FT_DELETED', 'BLACKHOLE', 'INNODB_SYS_TABLESTATS', 'MyISAM', 'INNODB_SYS_FOREIGN', 'INNODB_CMP_RESET', 'INNODB_SYS_COLUMNS', 'INNODB_BUFFER_PAGE_LRU']

The path wer Workbench is installed is:
C:\Program Files\MySQL\MySQL Server 5.6  <== 6, not 5 !!

How to repeat:
go to 'Server/Options file' in the menu of MySQL Workbench

Suggested fix:
it should look at the proper (existing) directory, which in this case is:
"C:\Program Files\MySQL\MySQL Server 5.6\"
[30 Dec 2013 7:27] MySQL Verification Team
Hello Luuk,

Thank you for the bug report.
Verified as described.

Thanks,
Umesh
[9 Jan 2014 1:16] Alfredo Kojima
Try deleting the connection and creating it again.
[9 Jan 2014 19:56] Luuk V
"Try deleting the connection and creating it again."

It's really dumb that i have to delete the connection after upgrading from one version of MySQL Wokbench to a newer version, which included an upgrade of MySQL.

Connection information should never be stored in a version specific directory!
[19 Sep 2014 22:38] Alfredo Kojima
Server configuration file is version specific, it has nothing to do with the connection.
The problem seems to be that you upgrade the server and the server information was not updated in WB, so it assumed it was still connecting to the same server (which is not the case).

We will add some checks in Windows, to try detecting that case.
[20 Sep 2014 9:47] Luuk V
> Server configuration file is version specific, it has nothing to do with the connection.
OK, i can live with that....

> We will add some checks in Windows, to try detecting that case.
Thanks!