Joomla! Forum - community, help and support

Doing an upgrade of Joomla 2.5.3 to 2.5.4 using the backend Extension Manager Update function I get the following errors.
This seems the same as the allegedly fixed {#27488] JInstaller: :Install: Error on upgrade 1.7.3 to 2.5 Beta 1 reported on joomlacode.org.


JInstaller: :Install: Error SQL DB function failed with error number 1062
Duplicate entry '22' for key 'PRIMARY' SQL=INSERT INTO `j16_menu` (`id`, `menutype`, `title`, `alias`, `note`, `path`, `link`, `type`, `published`, `parent_id`, `level`, `component_id`, `ordering`, `checked_out`, `checked_out_time`, `browserNav`, `access`, `img`, `template_style_id`, `params`, `lft`, `rgt`, `home`, `language`, `client_id`) VALUES (22, 'menu', 'com_joomlaupdate', 'Joomla! Update', '', 'Joomla! Update', 'index.php?option=com_joomlaupdate', 'component', 0, 1, 1, 28, 0, 0, '0000-00-00 00:00:00', 0, 0, 'class:joomlaupdate', 0, '', 41, 42, 0, '*', 1);
SQL =

INSERT INTO `#__menu` (`id`, `menutype`, `title`, `alias`, `note`, `path`, `link`, `type`, `published`, `parent_id`, `level`, `component_id`, `ordering`, `checked_out`, `checked_out_time`, `browserNav`, `access`, `img`, `template_style_id`, `params`, `lft`, `rgt`, `home`, `language`, `client_id`) VALUES
(22, 'menu', 'com_joomlaupdate', 'Joomla! Update', '', 'Joomla! Update', 'index.php?option=com_joomlaupdate', 'component', 0, 1, 1, 28, 0, 0, '0000-00-00 00:00:00', 0, 0, 'class:joomlaupdate', 0, '', 41, 42, 0, '*', 1);

Files Update: SQL error file DB function failed with error number 1062
Duplicate entry '22' for key 'PRIMARY' SQL=INSERT INTO `j16_menu` (`id`, `menutype`, `title`, `alias`, `note`, `path`, `link`, `type`, `published`, `parent_id`, `level`, `component_id`, `ordering`, `checked_out`, `checked_out_time`, `browserNav`, `access`, `img`, `template_style_id`, `params`, `lft`, `rgt`, `home`, `language`, `client_id`) VALUES (22, 'menu', 'com_joomlaupdate', 'Joomla! Update', '', 'Joomla! Update', 'index.php?option=com_joomlaupdate', 'component', 0, 1, 1, 28, 0, 0, '0000-00-00 00:00:00', 0, 0, 'class:joomlaupdate', 0, '', 41, 42, 0, '*', 1);
SQL =

INSERT INTO `#__menu` (`id`, `menutype`, `title`, `alias`, `note`, `path`, `link`, `type`, `published`, `parent_id`, `level`, `component_id`, `ordering`, `checked_out`, `checked_out_time`, `browserNav`, `access`, `img`, `template_style_id`, `params`, `lft`, `rgt`, `home`, `language`, `client_id`) VALUES
(22, 'menu', 'com_joomlaupdate', 'Joomla! Update', '', 'Joomla! Update', 'index.php?option=com_joomlaupdate', 'component', 0, 1, 1, 28, 0, 0, '0000-00-00 00:00:00', 0, 0, 'class:joomlaupdate', 0, '', 41, 42, 0, '*', 1);

Read this and you know how to resolve:

https://www.akeebabackup.com/documentat ... pdate.html

Leo

Many thanks - I will apply this.

Just for interest, is the database actually broken by this error or could it be ignored?

This error doesn't break the database. It only doesn't show the component joomlaupdate in the components menu in the backend. The suggested fix adds this to the menu.

Do verify the contents of administrator\components\com_admin\sql\updates\mysql\2.5.4-2012-03-19.sql. Those commands have to be executed as well.

Also verify #_schemas id 700. The version_id should start with 2.5.4.

Thanks sovainfo.

Running the sql you describe leads to error on first step (column access already exists), so have ignored this hoping that everything else is OK.
Schemas id 700 is correct already.

How did you get to know this stuff?

@tecpartner: I studied the code of com_admin.