MySQL Bugs: #69572: Workbench does not connect to a database and crash

Bug #69572	Workbench does not connect to a database and crash
Submitted:	25 Jun 2013 11:19	Modified:	16 Sep 2013 14:39
Reporter:	Roman Sidleja	Email Updates:
Status:	Duplicate	Impact on me:	None
Category:	MySQL Workbench	Severity:	S1 (Critical)
Version:	6.0.2.10924	OS:	Windows (Windows 8 Professional)
Assigned to:		CPU Architecture:	Any
Tags:	windows 8, workbench

Description:
Workbench crash after connect to database.

How to repeat:
Download msi installer or zip archive
Install it or extract it from zip archive
Run
Create connection to mysql server
Double click to created connection and workbench crash.
Eventlog: 
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
- <System>
  <Provider Name="Application Error" /> 
  <EventID Qualifiers="0">1000</EventID> 
  <Level>2</Level> 
  <Task>100</Task> 
  <Keywords>0x80000000000000</Keywords> 
  <TimeCreated SystemTime="2013-06-25T10:58:12.000000000Z" /> 
  <EventRecordID>5463</EventRecordID> 
  <Channel>Application</Channel> 
  <Computer>sirnb</Computer> 
  <Security /> 
  </System>
- <EventData>
  <Data>MySQLWorkbench.exe</Data> 
  <Data>6.0.2.10924</Data> 
  <Data>51b9d5a7</Data> 
  <Data>KERNELBASE.dll</Data> 
  <Data>6.2.9200.16451</Data> 
  <Data>50988950</Data> 
  <Data>e06d7363</Data> 
  <Data>00014b32</Data> 
  <Data>378</Data> 
  <Data>01ce7192dfb4dfca</Data> 
  <Data>C:\Program Files (x86)\MySQL\MySQL Workbench 6.0 CE\MySQLWorkbench.exe</Data> 
  <Data>C:\Windows\SYSTEM32\KERNELBASE.dll</Data> 
  <Data>203363b9-dd86-11e2-be79-c01885b7829f</Data> 
  <Data /> 
  <Data /> 
  </EventData>
  </Event>

The connection you created is for local server or remote?. Thanks.

Connection to mysql db was realized with the instance of putty with tunnel to remote computer where was running mysql DB.
Connection was tested by Workbench and marked as OK when I created new connection to the database.  
I also tried connect over connection method Standard TCPIP over SSH which was marked as OK, but the problem remained without change.

Please try the latest 6.0.5 version.

I have installed mysql workbench build 6.0.5.1116 and the problem with crash still remaining. Error in eventlog:
Aplikace: MySQLWorkbench.exe Verze Framework: v4.0.30319 Popis: Proces was terminated due to an unhandled exception. Exception information: Exception codee 06d7363, address 773A4B32

I'm also experiencing the same issue with Windows 7

Please try version 6.0.7. Thanks.

I have the same issue (crash on opening a SSH connection) in 6.0.7 on Windows XP SP3 (5.1.2600). I saw nothing interesting into the event log.

To add that there is no problem with local connections.

Some more information: I do NOT have a crash with remote SSH connectsion, if I check "Disable secure_auth" into connection's settings. I tried to test my connections settings (as Roman Sidleja wrote that this works), but I've received the following message "Connection using old (pre-4.1.1) authentication protocol refused (client option 'secure_auth' enabled)", so I've changed the settings and my existing connections (that were working in 5.2.47) work now. I'm not sure how this is related to the crash, but it seems disabling this helps.

I was able to repeat the crash with SSH connection when checking another bug report: http://bugs.mysql.com/bug.php?id=70332 . Thanks.

I confirm Georgi Sotirov's comment :

With MySQL Workbench 6.0.7.11215 trying to connect to an MySQL Server using an old (pre-4.1.1) authentication protocol, the behavior systematically depends on :
- the OS version, 
- the 'Disable secure_auth' checkbox of the connection's settings :

Each time MySQL Workbench 6.0.7.11215 with DEFAULT settings tries to connect to MySQL Server 5.0.95 :

- On MS-Windows 7, MySQL Workbench systematically crashes.

- On MS-Windows XP SP3, MySQL Workbench systematically displays following error message, which is really useful and leads to the workaround :
  Connection using old (pre-4.1.1) authentication protocol refused (client option 'secure_auth' enabled)

The cause of both failures is that, by default, MySQL Workbench 6.0.7.11215 enables 'secure_auth', but one can NOT know it before receiving the error message on MS-Windows XP SP3.

Each time MySQL Workbench 6.0.7.11215 with 'secure_auth' DISABLED in the connection's settings tries to connect to MySQL Server 5.0.95 :

- On MS-Windows XP SP3, MySQL Workbench systematically connects successfully.

- On MS-Windows 7, MySQL Workbench also systematically connects successfully.

http://bugs.mysql.com/bug.php?id=79132 marked as duplicate of this one.