Unsupported Screen Size: The viewport size is too small for the theme to render properly.

Error No 1043 – Bad handshake

forums › forums › SQLyog › Using SQLyog › Error No 1043 – Bad handshake

  • This topic is empty.
Viewing 24 reply threads
  • Author
    Posts
    • December 5, 2003 at 1:18 am #8266
      kengaun
      Member

      Hi ,

      I have upgraded MySQL to 4.1.1, when I tried to login using SQLyog (V3.62)

      encountered error message 1043 – Bad Hanshake…

      Please help to advise what is the error mean ?

    • December 5, 2003 at 2:27 am #15304
      Ritesh
      Member

      This is what MySQL AB has to say:

      Quote:
      The above situation can be caused by two issues only. One is

       malfunctioning in SSL protocol and the other one is incompatibility in

       password scrambling algorithms.

       

       As our Windows version does not have SSL, you have hit a problem in

       password scrambling.

       

       MySQL 4.1 has introduced a new password scheme, which utilizes much

       longer and much more secure passwords then version 4.0.

       

       If client library from version 4.0 is trying to authenticate a user

       with a new, long password, then it will fail, with a “Bad handshake”

       error.

      We will release SQLyog 3.64, as soon as we get an updated version of libmysql.dll from MySQL AB. This is going to be as early as next week

    • December 5, 2003 at 2:49 am #15305
      kengaun
      Member

      Hi,

      Just to add on. Before I upgrade MySQL, I have no problem in using SQLYog(V3.62) accessing MySQL 4.1.0.

    • December 5, 2003 at 8:19 am #15306
      Shadow
      Member

      Apparently MySql considered the security changes so important that they broke compatibility. It wasn't the first in v4.1's history and that's why we are not upgrading yet.

    • December 9, 2003 at 12:05 pm #15307
      Ritesh
      Member

      SQLyog 3.64 RC1 has been released. Check out http://www.webyog.com/forums/index.php?act…&st=0#entry1942

      This version uses the new libmysql.dll for connecting to MySQL 4.1.1.

    • December 10, 2003 at 3:35 am #15308
      kengaun
      Member

      Hi Ritesh,

      I have tested SQLyou 3.64 with MySQL 4.1.1, able to login the database without error.

      But when I tried to click alter table structure, it prompt with the message :-

      Could not read the table for the table!

      For your review.

    • December 17, 2003 at 8:40 am #15309
      kengaun
      Member

      Hi,

      Any update regarding the error message : Could not read the data for the table!

      when I tried to click alter table structure ?

    • December 17, 2003 at 9:50 am #15310
      Shadow
      Member

      From what version did you upgrade? Have you checked MySql's website for known bugs regarding this issue?

      This problem seems to be with Mysql and not SQLyog…

    • December 18, 2003 at 2:26 am #15311
      peterlaursen
      Participant

      se here: http://www.webyog.com/forums/index.php?act…ct=ST&f=6&t=664

      – as you se I have no problems !

      HOW did you upgrade to MySQL 4.1.1 and from which version ?

      When I DL'ed 4.1.1 it came without installer, so I Just stopped the service and WinmySQLAdmin, replaced the folder (of course not the folder “data”) then restarted WinMYSqlAdmin and the service. WinMySqlAdmin tells me that I run server version 4.1.1 so I believe that !

      I interpret your error message “Could not read the data for the table” as if the information in the “mysql”DB (or folder if you like) contains wrong or no information about your own user-DB.

      If you have a backup try to replace your “data” folder with the one from the backup. (close service and MySQLAdmin while doing this)

    • December 18, 2003 at 7:31 am #15312
      Shadow
      Member

      Perhaps kengaun should run the script that fixes the privileges…

    • December 18, 2003 at 8:57 am #15313
      kengaun
      Member

      Hi,

      I was upgraded MySQL from 4.1.0 to 4.1.1

      The updgrade was done as the steps mentioned by peterlaursen.

      I have attached the screen shots that I went through.

      Hope some helps from yours.

    • December 18, 2003 at 10:16 am #15314
      Shadow
      Member

      Did you fix the mysql db that stores the access rights?

    • December 18, 2003 at 11:54 am #15315
      Ritesh
      Member
      kengaun wrote on Dec 17 2003, 08:40 AM:
      Hi,

      Any update regarding the error message : Could not read the data for the table!

      when I tried to click alter table structure ?

      MySQL has changed the structure of result returned by “show table status…” in MySQL 4.1.1.

      We will be coming out with 3.64 RC2 by the end of this month. It will have all the bugs related to 4.1.1 fixed 😀

    • December 18, 2003 at 5:22 pm #15316
      peterlaursen
      Participant

      As you might have noticed, I upgraded from 4.0.13 to 4.1.1 with no problems.

      So it might be a problem with the 4.1.0 -version, that causes your problem?

      After all – it is an alpha!

    • December 31, 2003 at 10:42 am #15317
      peterlaursen
      Participant

      Just an information for those who read here ….

      It seems that SqlYog 3.64 RC1 works fine with the new Mysql ver. 5 alpha too.

    • January 3, 2004 at 10:49 am #15318
      Ritesh
      Member

      We have released SQLyog 3.64 RC2 that has lot of compatibility issues regarding MySQL 4.1.1 fixed. I will suggest that you upgrade from RC1 to RC2.

      You can download it from http://www.webyog.com/sqlyog/SQLyog364.exe

    • January 6, 2004 at 2:27 am #15319
      kengaun
      Member

      Hi Ritesh,

      Updated SQLyog to 3.64 RC2 and confirmed alter table error no longer appeared.

      Thanks…

    • January 7, 2004 at 7:24 am #15320
      peterlaursen
      Participant

      I can confirm kengaun's observatin … 🙁

      Mysql 5 – WinXP Home (danish version)

    • January 15, 2004 at 7:34 am #15321
      peterlaursen
      Participant

      With the new version of mysql 5.00a (dated 2004.01.11) and webyog 3.64 RC4 I don't experience the problem anymore!

      An sqloyg error message appears telling “couldn't read data for the table” but after clicking “OK” it actually does read and alterations to the table structure can be done!

    • January 15, 2004 at 12:45 pm #15322
      Ritesh
      Member
      Quote:
      An sqloyg error message appears telling “couldn't read data for the table” but after clicking “OK” it actually does read and alterations to the table structure can be done!

      Are you still getting the error?

    • January 17, 2004 at 2:39 am #15323
      peterlaursen
      Participant

      it's very funny but I do with some tables, not others.

      and it's very confusing – I can't reproduce things …

    • January 17, 2004 at 10:50 pm #15324
      Shadow
      Member

      Have you tried increasing the different timeout settings?

    • February 18, 2004 at 4:53 am #15325
      dito199
      Member

      Hi

      I am still getting Bad Handshake problem with 3.64 to mysql 4.1.1a. Presume its the libmySQL.dll issue. The current one in the 3.64 distribution is 5-Apr-2003.

      I have tried replacing it with libmySQL.dll from mysqllibopt folder (timestamp 19-Dec-2003). It is able to connect but Sqlyog coredump when I try to browse any database.

      Thx

      -WK-

    • February 18, 2004 at 5:34 am #15326
      Ritesh
      Member

      Check out the following thread –

      http://www.webyog.com/forums/index.php?act…0&hl=sqlyog364e

    • February 18, 2004 at 6:20 am #15327
      dito199
      Member

      v3.64e is good.

      Thx

      -WK-

  • Author
    Posts
Viewing 24 reply threads
  • You must be logged in to reply to this topic.