Support

There is an "Ignore most errors" checkbox in Kickstart and Akeeba eXtract Wizard. Try checking it before starting the extraction. Does that help?

Have you tried extracting these files locally, on your computer, before uploading them to your server?

The XAMPP version doesn't make any difference, actually. The extraction engine of Akeeba eXtract Wizard has not been modified since 2011. In fact you'll see that its release date is Sunday, 21 August 2011 18:54. There's another release (3.2) dating back in February 2011. That's as old as you can get.

Version 3.1 was an unsuccessful mess of PHP and Javascript code that never worked. Version 3.0 was exactly the same as 3.2. The only difference between 3.0 and 3.2 was that the former was compiled with Delphi 7 whereas the latter was compiled with Freepascal Lazarus. It's the same language, different compiler. The only reason for this change was that Delphi 7 would only run on Windows XP and at that point the very old machine I was using to compile it got its CPU fried :)

In so many words: try both eXtract Wizard 3.2 and 3.3.

If this didn't work and since you have the same extraction engine there are only two possibilities:

• The archive you are downloading is not the same one you restored two years ago and is genuinely broken.
• You either forgot to download some part or the file got corrupt in transfer.

The first one is anybody's guess and I'd be the last person to claim that human memory is infallible. We can't test it so let's try doing something about the second one.

Try downloading the files again. Do not use your browser, use a tool speciffically made for managing S3 storage. I recommend CyberDuck. After downloading the files please check their sizes and compare what is on your computer with what's on S3. They must match down to the byte count (do NOT trust the size in Kb, Mb, Gb – these are approximations which can even use a different base, i.e. 1000 vs 1024 bytes to the Kb).

If you still get a partial extraction we'll need to run Kickstart in debug mode to see what's going on. Edit kickstart.php and change the lines

// Uncomment the following line to enable Kickstart's debug mode
//define('KSDEBUG', 1);

to

// Uncomment the following line to enable Kickstart's debug mode
define('KSDEBUG', 1);

(That is, remove the double forward slash from the second line). These lines are at the top of the file, lines 33 and 34 in my latest build. Then run Kickstart normally. It will create a file called debug.txt. Please ZIP and attach it to your next reply.

I have no idea, to be honest. I believe you would also need to transfer the database as well.

It looks like you have a genuinely corrupt backup archive. All you can do is salvage as much information from it as you can. The installation directory contains your database. All other files can be more or less replaced, either from other backups or from the packages of the extensions.

For the database restoration you can go either the regular way (run the script in the installation directory) or the manual way (https://www.akeebabackup.com/documentation/akeeba-backup-documentation/unorthodox-emergency-restoration.html).

Does that help?

You're welcome!