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

Database Synchronization Wizard – Buffer Overrun

forums forums SQLyog Sync tools, Migration, Scheduled Backup and Notifications Database Synchronization Wizard – Buffer Overrun

  • This topic is empty.
Viewing 7 reply threads
  • Author
    Posts
    • #10184

      I am using the database synchronization wizard to synchronize two databases. I have root access to both. I can do whatever I want on both and it works just fine. But when I run the Synch Wizard I get the following:

      Microsoft Vision C++ Runtime Library

      Buffer overrun detected!

      Program: C:Program FilesSQLyog Enterprisesja.exe

      A buffer overrun has been detected which has corrupted the program's

      internal state. The program cannot safely continue execution and must

      now be terminated.

      I'm on v5.21

      Any ideas?

    • #23416
      peterlaursen
      Participant

      Please try 5.23 RC2 (just uploaded) and report results.

    • #23417

      That did it. Thank you very much. That was easier than I expected. 😀

    • #23418

      SqlYog recently had me update… I did (now on 5.25) and I am once again getting Buffer Overrun Detected errors. Any ideas?

    • #23419
      peterlaursen
      Participant

      We absolutely did not change anything in this respect!  So it is very strange what is happening here.

      Maybe a compiler/linker bug ?!

      would you mind try:

      http://www.webyog.com/downloads/betas/not_…d/SQLyog526.exe (community)

      http://www.webyog.com/downloads/betas/not_…QLyog526Ent.exe (registered)

      http://www.webyog.com/downloads/betas/not_…526EntTrial.exe (trial)

    • #23420
      peterlaursen
      Participant

      Are you sure that the overrun with 5.21 and 5.25 happens with exactly the same data where 5.23 is successfull?

      You can have more versions installed to different folders, so please verify again that this only depends on the program version and not the schema or data.

      I understand that this happens in the wizard.  

      At exactly what step of the wizard does it happen?

      Can you execute a sync job from commandline successfully?

      I also suggest that you attach the jobfile and a small SQL-dump (one for each host actually) to reproduce with.  

      Now we want to get to the bottom of this!

    • #23421

      Yes – the problem is happening with the same data. I only have one version of sqlyog installed.

      It happens whether I use the wizard or save the job file and run it from the command line.

      Attached are several files compressed in a zip file…

      sja from wizard.log – Obviously the log file from running the sync from the wizard

      sja from command line.log – the log file from running the sync by doing this: “C:Program FilesSQLyog Enterprisesja.exe” “C:Documents and SettingsPatrick FurgersonMy DocumentsSQLyog ScriptsSync PROD2BACK.xml” -l”C:Program FilesSQLyog Enterprisesja.log” -s”C:Program FilesSQLyog Enterprisesjasession.xml”

      sjasession.xml – the .xml file from the above

      Sync PROD2BACK.xml – the script file I used from the command line with the same settings as I run from the wizard.

      PROD Backup.sql – sql dump of the SOURCE database.

      BACKUP backup.sql – sql dump of the TARGET database.

      At first I thought it had to do with the fact that on the source database (prod) it seems to allow mixed case table names and on the target database (backup) it does not… so I fixed that problem but then it just hung on a different table.

      So I manually copied that table from source to target and then it would work through that table.

      But – then when it got down to the original table (though renamed all lower case) it hung again.

    • #23422
      adarsh
      Member

      reproduced here!

      thanks for giving the details. It is happening only for this table “ind1log” may be some data specific issue. we will fix this in next release.

      thanks.

Viewing 7 reply threads
  • You must be logged in to reply to this topic.