Upgrade Error ?

I have the following message during the last days of dolphin 7.2.1 What should I do?

There is a duplicate entry in the database table; see the very last line of the error message.  That will have to be corrected before you can continue with the upgrade.

what should I do?

Try to restore from backup and run it again, but before applying upgrade try to change upgrade/files/7.3.0.B2-7.3.0.RC/modules/videos/sql.sql file, by adding the following line:

...

DELETE FROM `sys_options` WHERE `kateg` = @iKatID;

DELETE FROM `sys_options` WHERE `Name` IN('category_auto_app_bx_videos', 'bx_videos_allowed_exts', 'bx_videos_max_file_size', 'bx_videos_profile_album_name', 'bx_videos_mode_index', 'bx_videos_number_index', 'bx_videos_number_home', 'bx_videos_number_all', 'bx_videos_number_top', 'bx_videos_number_related', 'bx_videos_number_previous_rated', 'bx_videos_number_albums_home', 'bx_videos_number_albums_browse', 'bx_videos_number_view_album', 'bx_videos_file_width', 'bx_videos_file_height', 'bx_videos_uploader_switcher');

...

It will make sure that everything is deleted, before inserting it on next lines.

If you have similar problems in other modules, let me know and I will provide instructions for them as well.

I just ran into this same exact issue; perhaps Boonex should break from not updating upgrades files and start fixing some of these upgrade issues as they appear so that people in the future won't face them.

I decided to take the time and study the upgrade scripts.  First of all, stop changing the sys_options sys_tmp_version before the upgrade script finishes; that should be done at the very end; it causes the database to say the version of Dolphin is at the next version when it is not; because the bloody script failed.

The upgrade script will skip a module without the sql.sql file; so for all the modules that have already been ungraded before the fail point, rename or remove the sql.sql file for those modules.  The upgrade will still report the modules as being upgraded because the script returns true.

In this case, add Alex's fix to both the video and sounds sql.sql file, replacing sounds for videos of course.

Then you have to make sure the database is reporting the correct version because the bloody script changes it before it starts updating the modules; it should do it last.  Once the database is back to the correct version, then revisit http://your_site.tld/upgrade and you will be able to start over.

It took a long time for the obvious to be stated.

~~~~~~~~~~~~~~~~~~~~~~
Michel ✈ Meta-Travel.com
~~~~~~~~~~~~~~~~~~~~~~

the update does not start

run this in the database.

UPDATE `sys_options` SET `VALUE` = '7.3.0.RC' WHERE `Name` = 'sys_tmp_version';

Just guessing you are trying to upgrade the 7.3 rc to final 7.3 version.

If you are going straight from 7.2.1  then change 7.3.0.RC  to 7.2.1....  

Then clean cache the cache folder 

then run the upgrade again.

It could be that you are not at the correct version for that upgrade.  I have to disagree with Dolphin Jay on telling you to set the value of the version in the database because we don't really know what version you are currently; if you are at 7.1.4 and run that update then it is not going to make things better.

We already update version as the last step, then modules are updated and modules versions are updated separately. 

header.inc.php file :

version.inc.php : 

<?php

$site['ver'] = '7.3';

$site['build'] = '0';

no version "sys_tmp_version" in sys_options 

I have every connection to the administration the "trial copy! Register and get a license it" , I have a valid license

Yes, and this is wrong.  Update modules and module versions and then when that has completed without errors, then update the site version.  You are updating the site version before modules have completed their upgrade and if the modules fail, then one has to go into the database and set the site version back before one can get the updates to run.

I ran into this same issue, the rows disappeared from the table along with the rows that hold the license.  I thought maybe I had done something to cause the rows to disappear.  Now I am wondering if the upgrade script had somehow deleted rows; It should just be doing a simple update.  I find it curious that you are also reporting the sys_options rows missing; the same rows that were deleted when I did the upgrade.

You will have to add the rows back to the sys_options table from your backup.  You can create a new database on your server and then import that database.  Then you can use phpMyAdmin or similar to export those rows and then import into the database.   If you are unsure of how to do this, then either myself or Dolphin Jay can help.

I don't know, you may just want to start over from backups but it is possible you can continue from where you left off.

In my last post I pulled the update right from the upgrade.sql file.  There is no drop and replace for the version number....

Not sure why yours is blank though.  Something failed for sure.  

If you need to get it back on track let me know and i can take a look at it. 

Dolphin Jay, read my reply, the part in red; this happened to me as well.  The problem, if you are asked to come in, is that the rows in the table were deleted by the upgrade procedure.  Strange but it has happened to me and lynxmondz so my guess is it is the upgrade script that caused this.

Version isn't deleted, it's updated. Are you sure that this record was in the db before the upgrade procedure ? Cn you try to check with some backup before the upgrade applied ?

I finally got around to upgrading my site and have just had the exact same issue so it must be the script and I cannot believe that it still has not been fixed. You have only had since May this year. 

Come on guys .....please sort it out.