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

Forum Replies Created

Viewing 3 posts - 1 through 3 (of 3 total)
  • Author
    Posts
  • sach97
    Member
    Ritesh wrote on Apr 11 2006, 11:24 AM:
    It would be really nice if you can mail the db to us. We will delete it from our system as soon as we are able to trace the issue. I think the problem is indeed due to the UCS-2 data.
    sach97
    Member
    peterlaursen wrote on Apr 10 2006, 09:52 PM:
    It is a pretty old verison you are using, I guess?

    Where did you get if from?

    Could I ask you to try 5.1 beta (trial also available here).

    This new version should fix issues with enocdings, as it issues a 'SET NAMES = uft8' on both servers.

    Are you using HTTP-tunnelling?

    If yes there may still be a problem (to be fixed in BETA 7), but I think we can fix it with hard-coding the tunnelling file …

    Hi tried it with Sqlyog Enterprise V5.1 Beta 6 but i am facing same problem. I have attached the job and log file. I have attached capuser.htm file for schema.

    D:Program FilesSQLyog Enterprise Trial>sja -lCapuser.log Capuser

    SQLyog Job Agent Version 5.1

    Copyright © Webyog Softworks Pvt. Ltd.. All Rights Reserved.

    Sync started at Tue Apr 11 10:33:24 2006

    Table SrcRows TgtRows Inserted Updated Deleted

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

    `capuser` 21 18

    D:Program FilesSQLyog Enterprise Trial>

    sach97
    Member
    Ritesh wrote on Apr 10 2006, 07:40 PM:
    Terminate button becoming invisible means that the background SJA process is over. If you execute SJA from the command line, the application should come out in between.

    What happens when you run SJA from the command line?

    Following is result from command line execution…

    D:Program FilesSQLyog Enterprise Trial>sja Capuser

    SQLyog Job Agent Version 5.01

    Copyright © Webyog Softworks Pvt. Ltd.. All Rights Reserved.

    Sync started at Mon Apr 10 20:36:22 2006

    Table SrcRows TgtRows Inserted Updated Deleted

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

    `capuser` 21 18

    D:Program FilesSQLyog Enterprise Trial>

    the table is create statement is and field PWD has encoded character.

    CREATE TABLE `capnew`.`capuser` (

    `CAPUserId` bigint(20) unsigned NOT NULL auto_increment,

    `GroupId` bigint(20) unsigned NOT NULL,

    `Name` varchar(20) character set ucs2 NOT NULL,

    `Email` varchar(255) character set ucs2 default NULL,

    `FullName` varchar(255) character set ucs2 default NULL,

    `PWD` varchar(255) character set ucs2 NOT NULL default '',

    `LastBookmarkId` bigint(20) unsigned default NULL,

    PRIMARY KEY (`CAPUserId`),

    UNIQUE KEY `Name` (`Name`),

    KEY `CAPUser_FKIndex1` (`GroupId`),

    CONSTRAINT `capuser_ibfk_1` FOREIGN KEY (`GroupId`) REFERENCES `usergroups` (`GroupId`)

    ) ENGINE=InnoDB DEFAULT CHARSET=latin1;

Viewing 3 posts - 1 through 3 (of 3 total)