Bug #70019 Updated to current version 6.06 and receive error on start.
Submitted: 13 Aug 2013 20:29 Modified: 9 Oct 2013 23:15
Reporter: josh biberdorf Email Updates:
Status: No Feedback Impact on me:
None 
Category:MySQL Workbench Severity:S1 (Critical)
Version:6.06 rev. 11184 OS:Microsoft Windows (8)
Assigned to: CPU Architecture:Any
Tags: exception

[13 Aug 2013 20:29] josh biberdorf
Description:
Receive error as soon as program initializes. Am not able to get past error message. Originally installed new version an update. Got error on start up of Workbench Then I did a full uninstall/reinstall of workbench and still experience the same issue.

How to repeat:
Happens every time I start it
[13 Aug 2013 20:32] josh biberdorf
Attempted to use "Report Bug" feature with no luck.

Error message: 
"MySQl Workbench has encountered a problem
External component has thrown an exception"

Is there an error log somewhere I can include?
[13 Aug 2013 20:33] josh biberdorf
Report Bug form seems to think the log in that I'm using right now is no good.
[14 Aug 2013 22:33] Alfredo Kojima
You can get  error logs in \Users\you\AppData\Roaming\MySQL\Workbench\log\
[15 Aug 2013 21:52] Andrew Clancey
I am having the same exact bug it seems.  Throws the error right away, and cannot report the bug.
[29 Aug 2013 12:06] Alfredo Kojima
Try renaming the Workbench folder in \Users\you\AppData\Roaming\MySQL\Workbench and starting WB again. If WB can start after that, pls send a zip of that folder (after reviewing it for any WB related private data you don't want to share).
[29 Aug 2013 12:15] Alfredo Kojima
Please also start WB from the command line with the following option and attach the wb.log file for it.

MySQLWorkbench.exe -log-level=debug3
[9 Sep 2013 23:15] Miguel Solorzano
Please try the work-around commented in the bug: http://bugs.mysql.com/bug.php?id=70262 . Thanks.
[10 Oct 2013 1: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".