Support

Site Restoration

#41609 restoration errors - For your information, the last error message was: Incorrect table name ''

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
8.2.27
CMS Type
Joomla!
CMS Version
4.4.10
Backup Tool Version
9.9.11
Kickstart version
8.0.6

Latest post by on Friday, 21 March 2025 15:17 CDT

Wednesday, 19 February 2025 04:45 CST

jfauntleroy

The first error that appears is shown is -

For your information, the last error message was: Incorrect table name ''

 

The restore process resumes and then it immediately responds with -

Database error processing line 0

Database server error reply:

ErrNo #1062

Duplicate entry '1377' for key 'josph_chronoforms_data_camp-registration-form.PRIMARY'

Raw query text:

INSERT INTO `josph_chronoforms_data_camp-registration-form`  VALUES 
('1377', '1184', '2023-01-28 01:24:00', '2023-06-11 18:56:10',

(Only a portion of the raw query text is shown here)


I have actually used phpMyAdmin to delete record 1377 from the restored table but then it just moves to the same error with 1378, etc. 
In fact, the table seems to be restored correctly when it is examined with phpMyAdmin. Unfortunately, no other tables get restored because
of repeated errors with this table.

I have also tried restoring using the 'REPLACE instead of INSERT' option selected and also tried deselecting 'Stop on CREATE error' and 
'Stop on other error' during other restoration attempts with this backup, The results are always the same errors that I have shown above.

Thanks for your help.

John


Edited by jfauntleroy on 2025-02-19 04:53 CST

Wednesday, 19 February 2025 04:54 CST

nicholas

You can select the option “Use REPLACE instead of INSERT” on the right hand side of the database restoration page to solve this problem.

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!

Wednesday, 19 February 2025 05:03 CST

jfauntleroy

I updated my original post to say that I have already tried to use the REPLACE instead of INSERT option with no success but you

probably responded before I edited the original post. The same error occurs.

As I also posted, I tried deselecting Stop on CREATE error and Stop on other error but the error is the same.

 

Wednesday, 19 February 2025 06:19 CST

jfauntleroy

I want to add that using the REPLACE instead of INSERT option does stop the 'Duplicate entry' error but the process fails at

the Incorrect table name '' error, then tries to Resume and after repeated Resume attempts it fails.

Wednesday, 19 February 2025 06:32 CST

nicholas

The way the restoration works is that the original table, if it exists, is first renamed or deleted depending on what you choose to do with existing tables.

Then, a new table is created. Following that, we run the INSERT commands.

What you are saying is that there is data in the table already, but that does not make sense. If the table wasn't renamed/dropped it could not be created – unless you deselect the Stop On CREATE Error option.

Even so, when you enable the Use REPLACE Instead of INSERT option then the restoration is no longer running INSERT commands, it's running REPLACE commands. The difference is that if a record with the same primary key exists, REPLACE overwrites it (it acts as an update), whereas INSERT throws an error. You cannot possibly get an error saying that an INSERT command failed when you have enabled this option.

If you got a message that the REPLACE command failed then the problem is with the database server. I don't know how it can be misconfigured to do that, honestly, but when REPLACE does not work the way it's documented to work then the only explanation is "server issue".

You also said that you disabled Stop On Other Error and you still get an error which is not possible. You are showing me the text of the reported exception which is not thrown when Stop On Other Error is disabled. If Stop On Other Error is disabled you do not reach the execution point where this text is generated.

If you are really selecting these options and they have no effect, something else is going on here. Probably something weird on the server. Can you try restoring on a different server, on a different host (or a self-hosted local server)? I am pretty sure the restoration will work there, showing us that something isn't right on the original server.

Are you using some kind of CDN, caching reverse proxy, or web server-level in front of your site? You will have to disable this while the restoration is in progress. You do not want to get cached results for the various requests taking place, the restoration won't work like that.

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!

Wednesday, 19 February 2025 08:16 CST

jfauntleroy

Thank you for the detailed response. I have been using Akeeba Backup and Kickstart with ANGIE for years without issues on many different sites.

While it doesn't make me an expert and does not rule out some error on my part, this is not something I have seen before and normally there is

no problem.

 

Per your suggestion, I just set up a new, empty Joomla site on a different server. I uploaded my backup file and kickstart to the site and started kickstart.

 

The first time, I tried with all of the default settings unchanged and received the same Incorrect table name '' message. Then after 30 seconds,

the process Resumed and I got the duplicate record error. 

 

I tried a second time and turned on REPLACE instead of INSERT and switched off the Stop on... options. The Incorrect table name '' error message appears

and the system retries every 30 seconds with the same Incorrect table name '' message appearing each time. Eventually the process times out and displays

the same message one last time but without the Cancel and Resume buttons or the countdown timer displayed.

 

Thanks

Wednesday, 19 February 2025 08:26 CST

nicholas

The first time, I tried with all of the default settings unchanged and received the same Incorrect table name '' message. Then after 30 seconds, the process Resumed and I got the duplicate record error. 

I think I start understanding what's going on. The "Incorrect table name ''" is actually important. I couldn't quite figure out what you meant in your original post, the formatting there me off.

Can you please ZIP and attach the backup log file? I have two suspicions about what is going on. One is that there is a table whose name is identical to the prefix, the other is that you were backing up on a case-insensitive filesystem with a mixed- or upper-case prefix. If neither is the case, the backup profile will at least help me understand why the restoration sees a table without a name, as I can see which table was backed up after #__chronoforms_data_camp-registration-form.

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!

Friday, 21 March 2025 15:17 CDT

System Task
system

This ticket has been automatically closed.

All tickets which have been inactive for a long time are automatically closed. If you believe that this ticket was closed in error, please contact us.

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!