Support

Site Restoration

#13458 installer connects but error in sql syntax

Posted in ‘Site restoration’
This is a public ticket

Everybody will be able to see its contents. Do not include usernames, passwords or any other sensitive information.

Environment Information

PHP version
n/a
CMS Type
Other
CMS Version
n/a
Backup Tool Version
n/a
Kickstart version
n/a

Latest post by nicholas on Thursday, 06 September 2012 11:13 CDT

Thursday, 06 September 2012 09:35 CDT

user68080
Mandatory information about my setup:

Have I read the related troubleshooter articles above before posting (which pages?)? Yes
Have I searched the tickets before posting? Yes
Have I read the documentation before posting (which pages?)? Yes
Joomla! version: 2.5.6
PHP version: 5.3.9 (host), don't know which on QNAP (but is newest firmware)
MySQL version: 5.0.95-community on host, 5.1.36 on QNAP Server
Host: www.barbalex.ch
Akeeba Backup version which took the backup: downloaded yesterday
Kickstart version used to extract the backup: downloaded today

Description of my issue:
I am trying to restore www.barbalex.ch on my local QNAP NAS.
I followed your guide and copied all the decompressed files to the web folder. The aakeba restoration pages open in the browser. Seems like connecting to the database works too. When I click on "vor" (next?) from the "DB" tab I get this error:

Fehler in der Zeile 0: CREATE TABLE `ApFloraFuerGis` ( `ArtNameLateinisch` varchar(255) default NULL, `ArtNameDeutsch` varchar(255) default NULL, `AktionsplanStatus` varchar(50) default NULL, `AktionsplanBeginnUmset ... MySQL: MySQL query failed with error 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 '�rApBerichtRelevant` varchar(60) default NULL, `TPopBekanntSeit` smallint(5) d' at line 1). The query was:CREATE TABLE `ApFloraFuerGis` ( `ArtNameLateinisch` varchar(255) default NULL, `ArtNameDeutsch` varchar(255) default NULL, `AktionsplanStatus` varchar(50) default NULL, `AktionsplanBeginnUmsetzung` smallint(5) default NULL, `AktionsplanStandUmsetzung` varchar(50) default NULL, `PopulationNr` int(10) default NULL, `PopulationName` varchar(150) default NULL, `PopulationStatus` varchar(50) default NULL, `PopulationBekanntSeit` smallint(5) default NULL, `TeilpopulationNr` int(10) default NULL, `TPop-Nr` varchar(255) default NULL, `TPopGemeinde` varchar(255) default NULL, `TPopFlurname` varchar(255) default NULL, `TPopBeschreibung` varchar(255) default NULL, `TPopStatus` varchar(50) default NULL, `TPopF�rApBerichtRelevant` varchar(60) default NULL, `TPopBekanntSeit` smallint(5) default NULL, `TPopXKoord` int(10) default NULL, `TPopYKoord` int(10) default NULL, `LinkZumAktuellenBericht` varchar(255) default NULL, `LinkZurDatenbank` varchar(255) default NULL, `MassgebendeTeilPop` tinyint(1) NOT NULL ) ENGINE=InnoDB DEFAULT CHARSET=utf8 COMMENT='Hilfstabelle. Stellt Daten von TPop f�r GIS bereit'

Seems to be a sql syntax error. Which I don't understand because my Site seems to work without errors. And I have previosly successfully restored the same database via sqldump file.
Could it be caused by the german characters like ü in the views? (there are none in the tables).
I choose utf8_general_ci as collation and also for the mysql connection (to host and to NAS).

Any hints how to tackle this problem?
Edited by user68080 on 2012-09-06 09:36 CDT

Thursday, 06 September 2012 09:42 CDT

nicholas
It seems to be caused by non-ASCII characters in the table fields and comment. I don't have a specific suggestion for working around this issue. Your only chance for restoring the site from the backup is using the emergency manual restoration procedure.

Nicholas K. Dionysopoulos

Lead Developer and Director

🇬🇷Greek: native 🇬🇧English: excellent 🇫🇷French: basic • 🕐 My time zone is Europe / Athens
Please keep in mind my timezone and cultural differences when reading my replies. Thank you!

Thursday, 06 September 2012 10:19 CDT

nicholas
For what is worth, I did a test using two different local sites and a live site. I added two special database tables:
CREATE TABLE `δοκιμή_με_utf8` (
  `id` int(11) unsigned NOT NULL AUTO_INCREMENT,
  `πατάρια` int(11) DEFAULT NULL,
  PRIMARY KEY (`id`)
) ENGINE=MyISAM DEFAULT CHARSET=utf8;

CREATE TABLE `überτεç†` (
  `id` int(11) unsigned NOT NULL AUTO_INCREMENT,
  PRIMARY KEY (`id`)
) ENGINE=MyISAM DEFAULT CHARSET=utf8;


As you can see I'm using a hell of a lot of UTF-8 characters from different UTF-8 regions. I'm trying very hard to cause the restoration to break... but I can't! It consistently restores the database, despite those funky table and column names. Akeeba Backup creates the files as UTF-8 (without BOM) and Akeeba Backup Installer restores them just fine.

So, in your case, we come down to one of these issues:
- Your Joomla! site does not run as UTF-8. I can't see that being possible with Joomla! 2.5.6. Besides, you wouldn't see any UTF-8 content on your site's pages.
- You used Kickstart's FTP mode and, somehow, the FTP server screwed up the files' encoding during transit.
- Something completely crazy that nobody can think of, like the filesystem encoding (after all, MySQL gets its table names from the database names when you're using the MyISAM database engine).

Can you try restoring the backup on a different server? This would tell us if the problem happens during backup or if there's something strange happening on your NAS.

Nicholas K. Dionysopoulos

Lead Developer and Director

🇬🇷Greek: native 🇬🇧English: excellent 🇫🇷French: basic • 🕐 My time zone is Europe / Athens
Please keep in mind my timezone and cultural differences when reading my replies. Thank you!

Thursday, 06 September 2012 11:07 CDT

user68080
o.k., will try and post the result here
Trouble is: I did not manage to install a server on my pc. There are conflicts with the ports and I am not an expert with configuring this stuff so I gave up after an hour poking around. That's why I'm trying on my NAS.
Thanks for quick and great help!

Thursday, 06 September 2012 11:13 CDT

nicholas
I may be able to help you with your port issues. If you're running Skype, shut it down before launching your local web server software. Skype binds port 80 by default – on top of its own higher ports... Problem: port 80 is assigned to web servers. Basically, Skype is doing something wrong.

Nicholas K. Dionysopoulos

Lead Developer and Director

🇬🇷Greek: native 🇬🇧English: excellent 🇫🇷French: basic • 🕐 My time zone is Europe / Athens
Please keep in mind my timezone and cultural differences when reading my replies. Thank you!

Support Information

Working hours: We are open Monday to Friday, 9am to 7pm Cyprus timezone (EET / EEST). Support is provided by the same developers writing the software, all of which live in Europe. You can still file tickets outside of our working hours, but we cannot respond to them until we're back at the office.

Support policy: We would like to kindly inform you that when using our support you have already agreed to the Support Policy which is part of our Terms of Service. Thank you for your understanding and for helping us help you!