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

4.2 Beta3 Sync – Unsuccessful..

forums › forums › SQLyog › SQLyog: Bugs / Feature Requests › 4.2 Beta3 Sync – Unsuccessful..

  • This topic is empty.
Viewing 9 reply threads
  • Author
    Posts
    • October 3, 2005 at 12:36 pm #9271
      sdozono
      Member

      I tested 4.2 Beta 3 (latest). Thank you for your hard work!

      🙂

      I tested synchronization over HTTP tunneling.

      Then,

      Error fetching source server version information.

      Check D:Program FilesSQLyog Enterprisesja.log for complete error details.

      There was an error while execute a query. The query and the error has been logged in the log file.

      in the log file.

      Error fetching source server version information.Error No. 12002

      HTTP Error.

      There is no problem with SQLyog 4.2 Beta2 with the same SQLyogTunnel.php.

    • October 3, 2005 at 1:30 pm #19387
      sdozono
      Member

      Additional Info.

      version()

      4.1.12

      [FedoraCore 4]

      version()

      4.1.7-nt

      [Windows XP]

      version( )

      4.0.22-standard

      [? ISP]

    • October 3, 2005 at 1:32 pm #19388
      peterlaursen
      Participant

      Confirmed.

      I get this error msg with 4.0.26 on local and 4.0.24 on remote:

      Quote:
      Error fetching target server version information.Error No. 12019

      HTTP Error. Denne handle har en forkert status til den valgte handling.

      Last half part is Danish and must be a Windows error-msg. Some protocol error.

      Translation somewhat like “The status for this handle is wrong for the action specified”.

    • October 3, 2005 at 2:36 pm #19389
      peterlaursen
      Participant

      I think you mismatched the installer build!

      Installation screen says beta4, but program help says beta 3.

      And error persists!

      😛

    • October 3, 2005 at 5:05 pm #19390
      peterlaursen
      Participant

      I just can add that problems also exist when tunnelling to a server running on windows.

    • October 6, 2005 at 1:00 am #19391
      sdozono
      Member

      I agree with peterlaursen. And, one more thing,

      >Webyog releases SQLyog v4.2 BETA 4.

      >This BETA has the following bug fixes.

      >– Fixed a bug with HTTP Tunneling as reported at >http://www.webyog.com/forums/index.php?showtopic=1718

      this is Not a problem of SQLyogtunnel.php.

      When I tried to copy DB Table from my local to remote MYSQL 4.0.23(With tunnel.php), I got this error.

      ==============

      Error No. 1064

      You have an error in your SQL syntax. Check the manual that corresponds to your MySQL server version

      for the right syntax to use near 'DEFAULT CHARSET=ujis' at line 5

      ==============

      This is a problem of SQLyog itself, I think…

      Thank you for your consideration in advance!

    • October 6, 2005 at 4:05 am #19392
      Ritesh
      Member

      http://www.webyog.com/forums/index.php?sho…63&st=0&p=7439&

      BETA 5 has the fix for the HTTP Tunneling issue.

      Quote:
      Error No. 1064

      You have an error in your SQL syntax. Check the manual that corresponds to your MySQL server version

      for the right syntax to use near 'DEFAULT CHARSET=ujis' at line 5

      This is because you are running v4.1 or above at your local machine. These MySQL versions support CHARSET options where as v4.0 and below does not. SQLyog uses MySQL's inbuilt CREATE TABLE SQL to generate & copy table structure from one database to another.

      If you note, the CREATE TABLE statement in v4.1 and above have CHARSET information included in it and thus the query fails in older MySQL versions.

      What you can do now is to use Structure Sync Tool to generate the SQL scripts and remove all the charset information from it. Execute the scripts again at your remote server.

    • October 6, 2005 at 4:57 am #19393
      Ritesh
      Member

      I have added this issue in the TO-DO list.

      We will fix this issue in one of the next v4.2 BETAS.

    • October 6, 2005 at 5:13 am #19394
      sdozono
      Member

      Ok. Thank you for your explanation. I understand.

      I checked Table copy from MYSQL 4.0.* to 4.0.*, there was no problem.

      And even dump file also can't be loaded directly from 4.1 to 4.0..

      P.S. Sync Succeeded with SQLyog 4.2 Beta5 !

      I couldn't connect to MYSQL at first, though, after rebooting my PC, it goes well!

      Thank you. 😆

    • October 6, 2005 at 12:31 pm #19395
      peterlaursen
      Participant
      Quote:
      I couldn't connect to MYSQL at first, though, after rebooting my PC, it goes well!

      Probably the TCP-stack got messed up in Windows, or something like that. I don't think it is a SQLyog issue.

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