| Bug #65353 | Unable to open MySQL Workbench | ||
|---|---|---|---|
| Submitted: | 17 May 2012 18:32 | Modified: | 30 Jun 2012 17:46 |
| Reporter: | Jugesh Sundram | Email Updates: | |
| Status: | No Feedback | Impact on me: | |
| Category: | MySQL Workbench | Severity: | S1 (Critical) |
| Version: | 5.2 CE | OS: | Windows (Windows 7) |
| Assigned to: | CPU Architecture: | Any | |
[17 May 2012 18:32]
Jugesh Sundram
[17 May 2012 20:22]
MySQL Verification Team
Are you using version 5.2.40? Otherwise please upgrade. Thanks.
[25 May 2012 14:26]
Nathan Walsh
I have the same problem. My version is 5.2.40 and it crashes on open (unhandled MS.NET exception error) I am running Windows 7 x64 Problem signature: Problem Event Name: APPCRASH Application Name: MySQLWorkbench.exe Application Version: 5.2.40.8790 Application Timestamp: 4fa2f938 Fault Module Name: wbprivate.be.dll Fault Module Version: 0.0.0.0 Fault Module Timestamp: 4fa2f597 Exception Code: c0000005 Exception Offset: 000b954e OS Version: 6.1.7601.2.1.0.256.48 Locale ID: 1033 Additional Information 1: 0a9e Additional Information 2: 0a9e372d3b4ad19135b953a78882e789 Additional Information 3: 0a9e Additional Information 4: 0a9e372d3b4ad19135b953a78882e789 Read our privacy statement online: http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409 If the online privacy statement is not available, please read our privacy statement offline: C:\Windows\system32\en-US\erofflps.txt
[25 May 2012 15:11]
Nathan Walsh
found the solution in bug 50216 [11 Jan 2010 11:20] Johannes Taxacher Hi Robert, did you have a previous version of MySQL Workbench installed on the machine before installing the 5.2.11 release?. Please try to delete the following directory and check if WB then starts correctly: C:\Users\<yourusername>\AppData\Roaming\MySQL\Workbench
[30 May 2012 17:46]
Armando Lopez Valencia
Hello Jugesh. Can you please try Nathan suggestion and let us know if it solve your problem? Thanks.
[1 Jul 2012 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".
