Bad Handshake

Discussion of open issues, suggestions and bugs regarding database management and administration tools for MySQL
Post Reply
hashmi
Posts: 1
Joined: Tue 10 May 2011 20:41

Bad Handshake

Post by hashmi » Tue 10 May 2011 20:47

After I upgraded to latest MySQL 5.5.12 on Windows 64 bit I am getting a "Bad Handshake" prompt when I click to connect to that database.

Navicat is installed on the same machine and it is connecting normally as it used to do before upgrade.

Syed Hashmi

.jp
Devart Team
Posts: 345
Joined: Wed 09 Sep 2009 06:55
Location: devart

Post by .jp » Wed 11 May 2011 10:31

Thanks for the post.
Our QA team has reproduced this error and we are going to fix it in the next build of the tool.
As a workaround, please change the created connection (or create a new one), and leave the "Database" field in the "Database Connection Properties" window blank.

markm9999
Posts: 20
Joined: Wed 03 Feb 2010 14:42

Post by markm9999 » Mon 16 May 2011 13:14

This is a MAJOR pain. I'm still @ 4.50.348. When the update is released, will it be available in v4.50?

.jp
Devart Team
Posts: 345
Joined: Wed 09 Sep 2009 06:55
Location: devart

Post by .jp » Mon 16 May 2011 13:24

markm9999 wrote:This is a MAJOR pain. I'm still @ 4.50.348. When the update is released, will it be available in v4.50?
The fix will be available in dbForge Studio for MySQL, v5.0 only.
By the way, dbForge Studio for MySQL, v4.50 does not support MySQL Server v5.5.xx at all.

markm9999
Posts: 20
Joined: Wed 03 Feb 2010 14:42

Post by markm9999 » Tue 17 May 2011 14:00

It might not be 'supported', but so far I have not run into any compatibility issues. :wink:

I will however be upgrading to v5.0, especially since many of the features I suggested are now in this version :D (yes, i'm that markm!)

Any eta on the fix for this? Keep up the great work on this product!

Cheers!
Mark

.jp
Devart Team
Posts: 345
Joined: Wed 09 Sep 2009 06:55
Location: devart

Post by .jp » Tue 17 May 2011 14:56

...especially since many of the features I suggested are now in this version...
We are trying to implement as many features suggested by users as possible. Please take part in voting for the new features for the next version of dbForge Studio here:
http://devart.uservoice.com/forums/7729 ... -for-mysql
Any eta on the fix for this?
I have to say that it was an unexpected error for us. We have tested out tool to work with MySQL 5.5.5, 5.5.9, 5.5.11 and haven't got any errors until MySQL 5.5.12. So, we have already fixed it and the release of the new build with fixes will be available tomorrow.

.jp
Devart Team
Posts: 345
Joined: Wed 09 Sep 2009 06:55
Location: devart

Post by .jp » Thu 19 May 2011 06:19

to hashmi and markm9999
The build with fixes is on the site. Please download it.

NoComprende
Posts: 135
Joined: Tue 09 Jan 2007 13:44

Post by NoComprende » Fri 13 Apr 2012 15:25

I've just upgraded to MySQL 5.5 and I'm using MyDAC 5.90.0.60 for rad studio 2009 and I'm getting this error. Where can I find the fix?

AndreyZ

Post by AndreyZ » Tue 17 Apr 2012 12:47

The "BAD HANDSHAKE" error was fixed in MyDAC 6.10.0.7. To solve the problem, you should upgrade MyDAC at least to this version. When you buy MyDAC you receive a registration mail where you can find a link, username and password for Registered Users' Area. If there is no link in Registered Users' Area to download MyDAC 6.10.0.7 (or higher), it means that your subscription is expired and you need to renew it. You can renew your subscription here (on the Renewals & Upgrades tab, in the Subscription Renewals section): http://www.devart.com/mydac/ordering.html . After subscription renewal you will be able to download MyDAC 6.10.0.7 from Registered Users' Area.

Post Reply