Support

It seems my restore loads the file and the database and then fails on the last step - step 7 on adding the admin record as a user. I have made the backup with both jpa and zip formats, and both 2.3 and 2.2 versions. Is this a sign of an error in the production site database that is preventing a complete backup? No errors are reported during the backup process. Screenprint here:
Thanks for any ideas !!!!

I want to be sure I understand where the error is occurring. The database restore finishes, correct? Is the new information written to the configuration.php file? I think that is where it is failing. Is this restore to the same server or a different server?

I'm not sure of the sequence of events under the covers.

a) This is a backup from a Rochen server (production) being restored to an XAMPP server on Vista (development), a process I have done numerous times and the first time I had problems was in moving to 2.3 stable (from 2.2.1) - I have since uninstalled 2.3 and reinstalled 2.2.1. The Xampp server had a working copy of the same site that was less than a week old that was being overwritten.

b) The backup log appears unremarkable to an untrained eye.

c) The file unpack works flawlessly

d) The database unpacks fine to the MySQL database using root / no password - end of file reached.

e) The FTP screen is left at defaults

f) Step 6, the usual admin password is added to the prefilled information.

g) The error appears on the step 7. Finish screen.

I used the CPanel MySQL interface to run a database check of the source database and no issues were identified / the source db files should be fully readable. The total jpa size is 13Mb, the database is 1.5 Mb.

This is the same site that had an issue moving from dev. to production using 2.3 with the reportedly 'insufficient disk space' issue that was solved by rolling back to 2.2.1 Could 2.3 have left any droppings that impacted the database?

Thanks for any ideas.

Does the local site display properly and can you log in as admin?

The local site doesn't display at all - the installer simply starts over at the beginning.

Taking the next step and renaming the installation folder produces a white screen with JError - database driver missing or corrupt.

I moved on by completely deleting the XAMPP, extracting a clean one - presuming the driver file is inside the XAMPP installation or the database file was corrupt somehow. Re-ran kiskstart and was successful unpacking a 2.2.1 backup. I haven't tried 2.3 again for fear it caused the corruption and I'm behind on getting work done. I'll try it again in a few days to see if I can recreate and isolate the issue for you.

The "JError" indicates to me that it was probably a Joomla! issue, not am XAMPP issue. Nicholas has been trying to run down a problem with db.php, but is having problems getting the feedback he needs on it.

Nicholas released 2.3.1 this morning, which fixes several errors, one critical. If you are in a time crunch, stick with 2.2.1 and let somebody else test 2.3.1. (I can't believe I said that! :o )