Support

Akeeba Backup for Joomla!

#8771 Error installing upgrade

Posted in ‘Akeeba Backup for Joomla! 4 & 5’
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

Joomla! version
n/a
PHP version
n/a
Akeeba Backup version
n/a

Latest post by nicholas on Friday, 14 January 2011 13:24 CST

user18741
Had 3.1.5 on the site, clicked on the upgrade available, and the installer gave an error. I've attached a text version of the JInstaller error report copied from the Firefox window.

UPDATE- I also tried downloading the component from AkeebaBackup.com and then installing it via the Joomla installer from admin, and still get that error.

IN the admin if I select AkeebaBackup from the component menu I see:
404 - An error has occurred.
Component Not Found

I then tried to install AkeebaBackup, it still showed as 3.1.5 in the Extension Manager, and got this error when trying to uninstall it so I could start over new.

* Component Uninstall: SQL error or missing or unreadable SQL file. DB function reports no errors
* It was not possible to delete the selected file.: 'js'
* It was not possible to delete the selected file.: 'theme'
* It was not possible to delete the selected file.: 'icons'
* It was not possible to delete the selected file.: 'plugins'
* It was not possible to delete the selected file.: 'en-GB.com_akeeba.ini'
* It was not possible to delete the selected file.: 'en-GB.com_akeeba.ini'
* It was not possible to delete the selected file.: 'en-GB.com_akeeba.menu.ini'

I will stop now and wait to hear back from you, really need to get this backup system working again for the customers that need it will call me and I'll have to have them wait, not good.

user18741
I upgraded a different site, that was only one version back just fine. From 3.2.b3 to 3.2.b4 on the same servers, (shared hosting)

nicholas
Akeeba Staff
Manager
What is the error you get during installation? It sounds like a problem with your Joomla! installation, not the update script. The update script simply downloads the Akeeba Backup installation package from our servers and calls Joomla!'s com_installer to perform the actual installation. It sounds like com_installer dropped the ball and deleted the component's files without installing the new version. If you give me the exact installation (NOT uninstallation) error message I might be able to help you.

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!

user18741
here's the file I attached to the first post, sorry
* JInstaller::install: SQL Error. DB function failed with error number 1074
Too big column length for column 'remote_filename' (max = 255). Use BLOB instead SQL=CREATE TABLE IF NOT EXISTS `jos_ak_stats` ( `id` bigint(20) unsigned NOT NULL auto_increment, `description` varchar(255) NOT NULL, `comment` longtext, `backupstart` timestamp NOT NULL default '0000-00-00 00:00:00', `backupend` timestamp NOT NULL default '0000-00-00 00:00:00', `status` enum('run','fail','complete') NOT NULL default 'run', `origin` VARCHAR(30) NOT NULL DEFAULT 'backend', `type` VARCHAR(30) NOT NULL DEFAULT 'full', `profile_id` bigint(20) NOT NULL default '1', `archivename` longtext, `absolute_path` longtext, `multipart` INT NOT NULL DEFAULT 0, `tag` VARCHAR(255) NULL, `filesexist` TINYINT(3) NOT NULL DEFAULT '1', `remote_filename` varchar(1000) DEFAULT NULL, `total_size` bigint(20) NOT NULL DEFAULT '0', INDEX `idx_fullstatus`(`filesexist`, `status`), INDEX `idx_stale`(`status`, `origin`), PRIMARY KEY (`id`) );
SQL =

CREATE TABLE IF NOT EXISTS `jos_ak_stats` (
`id` bigint(20) unsigned NOT NULL auto_increment,
`description` varchar(255) NOT NULL,
`comment` longtext,
`backupstart` timestamp NOT NULL default '0000-00-00 00:00:00',
`backupend` timestamp NOT NULL default '0000-00-00 00:00:00',
`status` enum('run','fail','complete') NOT NULL default 'run',
`origin` VARCHAR(30) NOT NULL DEFAULT 'backend',
`type` VARCHAR(30) NOT NULL DEFAULT 'full',
`profile_id` bigint(20) NOT NULL default '1',
`archivename` longtext,
`absolute_path` longtext,
`multipart` INT NOT NULL DEFAULT 0,
`tag` VARCHAR(255) NULL,
`filesexist` TINYINT(3) NOT NULL DEFAULT '1',
`remote_filename` varchar(1000) DEFAULT NULL,
`total_size` bigint(20) NOT NULL DEFAULT '0',
INDEX `idx_fullstatus`(`filesexist`, `status`),
INDEX `idx_stale`(`status`, `origin`),
PRIMARY KEY (`id`)
);

* Component Install: SQL error or missing or unreadable SQL file. DB function failed with error number 1074
Too big column length for column 'remote_filename' (max = 255). Use BLOB instead SQL=CREATE TABLE IF NOT EXISTS `jos_ak_stats` ( `id` bigint(20) unsigned NOT NULL auto_increment, `description` varchar(255) NOT NULL, `comment` longtext, `backupstart` timestamp NOT NULL default '0000-00-00 00:00:00', `backupend` timestamp NOT NULL default '0000-00-00 00:00:00', `status` enum('run','fail','complete') NOT NULL default 'run', `origin` VARCHAR(30) NOT NULL DEFAULT 'backend', `type` VARCHAR(30) NOT NULL DEFAULT 'full', `profile_id` bigint(20) NOT NULL default '1', `archivename` longtext, `absolute_path` longtext, `multipart` INT NOT NULL DEFAULT 0, `tag` VARCHAR(255) NULL, `filesexist` TINYINT(3) NOT NULL DEFAULT '1', `remote_filename` varchar(1000) DEFAULT NULL, `total_size` bigint(20) NOT NULL DEFAULT '0', INDEX `idx_fullstatus`(`filesexist`, `status`), INDEX `idx_stale`(`status`, `origin`), PRIMARY KEY (`id`) );
SQL =

CREATE TABLE IF NOT EXISTS `jos_ak_stats` (
`id` bigint(20) unsigned NOT NULL auto_increment,
`description` varchar(255) NOT NULL,
`comment` longtext,
`backupstart` timestamp NOT NULL default '0000-00-00 00:00:00',
`backupend` timestamp NOT NULL default '0000-00-00 00:00:00',
`status` enum('run','fail','complete') NOT NULL default 'run',
`origin` VARCHAR(30) NOT NULL DEFAULT 'backend',
`type` VARCHAR(30) NOT NULL DEFAULT 'full',
`profile_id` bigint(20) NOT NULL default '1',
`archivename` longtext,
`absolute_path` longtext,
`multipart` INT NOT NULL DEFAULT 0,
`tag` VARCHAR(255) NULL,
`filesexist` TINYINT(3) NOT NULL DEFAULT '1',
`remote_filename` varchar(1000) DEFAULT NULL,
`total_size` bigint(20) NOT NULL DEFAULT '0',
INDEX `idx_fullstatus`(`filesexist`, `status`),
INDEX `idx_stale`(`status`, `origin`),
PRIMARY KEY (`id`)
);

Is that what you needed?

nicholas
Akeeba Staff
Manager
You seem to have an antiquated version of MySQL. Which version of MySQL are you using?

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!

user18741
You are correct that install somehow got put onto MySQL 4 !! I'm building a new one, with Joomla 1.6 on that host this AM, surprised me indeed!

nicholas
Akeeba Staff
Manager
I am glad I was able to pinpoint the problem. I hope you can use MySQL 5 on that site :)

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!