MySQL Bugs: #69464: Bug #59198 Error starting MySQL Workbench Server Administration

Bug #69464	Bug #59198 Error starting MySQL Workbench Server Administration
Submitted:	14 Jun 2013 5:16	Modified:	6 Sep 2013 22:33
Reporter:	S C	Email Updates:
Status:	No Feedback	Impact on me:	None
Category:	MySQL Workbench	Severity:	S3 (Non-critical)
Version:	5.2.47 CE Revision:10398	OS:	Windows (Windows 8, WIndows Server 2012)
Assigned to:		CPU Architecture:	Any
Tags:	attribute, AttributeError, NoneType, parametervalues

Description:
Bug #59198 isn't fixed but closed and I am re-opening it.

I just installed MySQL community server with workbench on several computers recently. Connections are all localhost based working along with IIS.

I found that on first run, things work fine through MySQL workbench. I opened up Server Administration and did some config. It was ok, and then I restarted the computers. I reopened Server Administration through workbench, e.g. clicking on "Manage Security", I got the error message as described in Bug #59198.

However, when I create another Server Instance, things work normally with another instance. The default instance can never be opened but to be deleted.

This happens to all my recent installations on multiple computers. So, it's not an accidental bug as described by [5 Jan 2011 9:00] Mike Lischke in Bug #59198.

How to repeat:
1. Install MySQL Community Server with MySQL workbench.
2. Open MySQL workbench. Check that there is a default server instance and use that for now. Set up root and other user settings with "Manage Security"
3. Fiddle around different things for a while, like creating databases, connecting MySQL from web server, etc... (Sorry, I can't remember what exactly I did in common on different machines.)
4. Restart computer. (Probably you just need to restart mysql server. I don't know if restarting computer is required. Sorry. )
5. Open MySQL workbench again. Select the default server instance and click on "Manage Security".
6. The Admin panel is unable to open and an error message pops on. It should read just like Bug #59198 says.

Suggested fix:
I am not sure if this is a problem with the server core or a problem with the workbench. The default server instance is always problematic. I haven't looked in depth what is causing this.

My suggestion for a temporary workaround is to create another server instance and dump the default server instance. I know... this isn't elegant but it's the only workaround I can think of until the MySQL development team does something about this.

Please attach the wb.log file produced when the error occurs. You can see where they're located through the Help menu

I am sorry. It has been a week since we first encountered the problem and we have applied my workaround for the machines last week. The log files have been deleted on the 16th of June before our periodic backup procedures. Therefore, I am unable to retrieve the log files for you.

Please reopen the bug when you're able to repeat the problem and attach the log file. We're unable to fix bugs unless we can repeat the problem ourselves.

For goodness sake, this is so easy to reproduce. Just because there are no provided log files, it doesn't mean you cannot reproduce the problem with ease. Just spend a little time on Google and you can see this bug has existed for quite some time throughout different MySQL workbench versions, and there have accumulated quite a handful of people complaining about it. Please don't ignore this bug with a light thought. 

I happened to be installing MySQL workbench on a test server today. With a fresh download of MySQL workbench and a quick installation, the problem occurred again within my expectation. I have uploaded the log files. Please take a look seriously. Any help will be truly appreciated. I can't bear to report to my supervisor with my quirk/workaround applying everytime.

I understand the bug is easy to reproduce for you, but it's not for us. We run WB in a variety of systems and environments and obviously, it doesn't happen for us. There is something specific in your environment that produces the problem which we have to narrow down and we won't be able to do so without your help.

Please try version 6.0.5 and if the problem still occurs, create a backup of your connection files using Tools -> Configuration -> Backup Connections... and send the zip file (after you verify that there is no sensitive data contained). Thanks!

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".