@Stevec4 The error is caused by the last SQL update here https://github.com/joomla/joomla-cms/blob/3.10-dev/administrator/components/com_admin/sql/updates/mysql/3.10.0-2021-05-28.sql using a hard-coded ID value and not leaving away the ID so the auto-increment would be used. This caused the statement not to succeed, and since it does not change database structure it has also not been run by the "Fix" button, which only fixes data structure changes. => Ping @zero-24 for information.

Therefore, to make your update to 3.10 RC complete, please run the following SQL statement e.g. in phpMyadmi, replacing the "#__" by your actual table prefix:

INSERT INTO `#__extensions` (`package_id`, `name`, `type`, `element`, `folder`, `client_id`, `enabled`, `access`, `protected`, `manifest_cache`, `params`, `custom_data`, `system_data`, `checked_out`, `checked_out_time`, `ordering`, `state`) VALUES
(0, 'plg_quickicon_eos310', 'plugin', 'eos310', 'quickicon', 0, 1, 1, 0, '', '{}', '', '', 0, '0000-00-00 00:00:00', 0, 0);

This will complete the installation of the End Of Service notification plugin.

You should do that if you plan to use that 3.10 RC 1 for developing your real life site.

If you only did that update to 3.10 RC for testing purpose and not plan to use the updated site for a real production site, you don't need to do that.

I will meanwhile prepare a fix so in future updates from 3.9.x to the next 3.10 RC 2 will not have that problem anymore.

@Stevec4 P.S.: Could you check e.g. with phpMyAdmin or in the extension manager in backend and report back which extension uses the record with extension_id= 496? Please report back name, type, element, folder and client_id of this extension. Thanks in advance.

Hi Richard
Thank you for the SQL fix I was just testing the install but applied it none the less.
Looks like extension id 496 is mod_latestactions, type is module, element is mod_latestactions, folder is blank and id is 496.

Let me know if I can provide any other info.
Steve

Let me know if I can provide any other info.

@Stevec4 No, that's sufficient. Thanks for reporting the issue and answering my questions. Am working on a fix for the next 3.10 RC 2.

@Stevec4 Do you have any idea how it comes that the extension id 496 is mod_latestactions? In the update SQL script 3.9.0-2018-05-20.sql we inserted it with id 319 when updating an older version to 3.9.0, and I can't see that this has ever changed.

Could you check if you have an extension with extension id 319 and if yes, what kind of module it is?

Pull request for the fix is #35034 . It has still draft status because I have to write testing instructions, but the code changes are already finished.

Closing as having a pull request. Please test #35034 . Thanks in advance.