MySQL Bugs: #69165: Error Starting Workbench Administrator

Bug #69165	Error Starting Workbench Administrator
Submitted:	7 May 2013 16:55	Modified:	9 May 2013 20:11
Reporter:	Greg Redl	Email Updates:
Status:	Can't repeat	Impact on me:	None
Category:	MySQL Workbench	Severity:	S2 (Serious)
Version:	5.2.47	OS:	Windows (2008 Enterprise x64)
Assigned to:		CPU Architecture:	Any

Description:
Environment:
Windows Server 2008 Enterprise x64
MySQL Community 5.6.10.1 - new installation

Due to requirements of a 3rd party software I need to set the transaction-isloation = READ-COMMITTED.
Since doing so, I can no longer access 'Manage Import/Export' or 'Manage Security'.  Luckily I do have access the the MySQL CLI.

Reversing this configuration does not restore the functionality either.

Can anyone provide a solution to restoring this functionality within WorkBench?

How to repeat:
Below are the steps to recreate:

1. Install MySQL Community 5.6.10.1
2. Modify the file C:\ProgramData\MySQL\MySQL Server 5.6\my.ini by adding "transaction-isolation = READ-COMMITTED" to the end of the file.
3. Restart the MySQL56 service
4. Launch MySQL WorkBench and select either 'Manage Security' or 'Manage Import/Export'

Reversing the my.ini modification does not restore those areas in Workbench.

Workbench Working

Attachment: read_commited.png (image/png, text), 121.20 KiB.

I couldn't repeat on Windows 7 64-bit. See prior screen-shot attached (1 instance showing the my.ini file and the other instance showing the Manage Security).

I have attempted this same process on 3 Windows Server 2008 machines, and end up with the same results.
I too had set one of them for READ-COMMITTED within WorkBench and restarted the MySQL56 service.  After that, I could no longer access the WorkBench Administrator.
I have attached the my.ini file from one of my instances.

config file after making the changes for READ-COMMITTED

Attachment: my.ini (application/octet-stream, text), 13.96 KiB.

Additionaly I ran the installer on a clean Windows 7 machine and obtained the same results:
1. EULA - accept [Next]
2. Find Latest Products - [Execute][Next]
3. Choose a Setup Type - Custom [Next]
4. Feature Selection
   Applications - deselect MySQL Notifier and MySQL For Excel
   Documentation - deselect all
   [Next]
5. Check Requirements - [Next]
6. Installation Progress - [Execute][Next]
7. Configuration Overview - [Next]
8. MySQL Server Configuration
   Server Configuration Type = Server Machine
   All other options left at defaults
   [Next]
   Root Account Password = <password>
   [Next]
   Windows Service Details - left at defaults
   [Next], [Next], [Finish]
9. Open MySQL Workbench and access 'Manage Security' > Config 
10. Enable transaction-isolation as READ-Committed within Options File > Advanced
11. [Apply]
12. Restart the MySQL56 service
13. Attempt to access the 'Manage Security' in Workbench recreates the error

This is now the 4th machine where I lose access to these areas on after statically setting the transaction-isolation.  I can offer a remote support session in order to try and get this issue resolved.

I am still unable to get WorkBench to cooperate.  And now, I cannot run queries against the database due to Workbench crashing continually after providing my login credential.

I really need a resolution for this.