Page 1 of 1

recover xampp directory from raw-data backup to new PC

PostPosted: 17. October 2017 22:54
by itsme33
Pals,

I've my previous laptop crashed, my xampp folder with all databases and everything was being copied as raw-files as backup each while, now I've copied from my backup location to a new Windows... version was 1.7.7 (php 5.3.8) installation package... now doesn't work at all on new PC.

I've tried xampp_setup.bat says can't find php.cli - tried copying files from new package of xampp (also version 1.7.7) no luck... I want to make it work on the new windows as I have many databases already there...

any idea? Kindly advise.

Re: recover xampp directory from raw-data backup to new PC

PostPosted: 17. October 2017 23:46
by Altrea
Hi,

without any helpful (and full) error messages, it is impossible to tell you anything about your issue.

best wishes,
Altrea

Re: recover xampp directory from raw-data backup to new PC

PostPosted: 18. October 2017 11:07
by itsme33
hello, thanks for your reply. there is no error logs, just think of it copying the entire directory of xampp from one pc to another, clicking on xampp_setup.bat does no effect in logs, only in the command line says this:

Sorry ... cannot find php cli!
Must abort these process!
Press any key to continue . . .

error logs in apache folder doesn't generate new files and doesn't update them with new dates..

please help, if this is possible to operate the xampp again as it was was, because I want the databases.. i have anther version of xampp 1.7.7 zip package.. can i use it or make a mix to let it work..

Re: recover xampp directory from raw-data backup to new PC

PostPosted: 18. October 2017 19:26
by Altrea
itsme33 wrote:there is no error logs, just think of it copying the entire directory of xampp from one pc to another, clicking on xampp_setup.bat does no effect in logs, only in the command line says this:

Sorry ... cannot find php cli!
Must abort these process!
Press any key to continue . . .

Do you start this file by double click or with enhanced administrator rights (rightclick -> run as administrator)?
This is still not the entire output of this file.
But It is not clear if executing the setup_xampp.bat file will do anything.

Have you tried to start the XAMPP control panel? What is it's log output?

itsme33 wrote:i have anther version of xampp 1.7.7 zip package.. can i use it or make a mix to let it work..

yes, this is technically possible. simply extract the entire fresh xampp version and copy over the \htdocs\ and \mysql\data\ folders from your not working xampp installation.

Re: recover xampp directory from raw-data backup to new PC

PostPosted: 19. October 2017 01:11
by itsme33
Thanks again for your reply Altrea. I was using Run as administrator anyway and gives that message Sorry can't find php cli!....

Now the strange this I've renamed my older directory... restarted the laptop, extracted new package 1.7.7 (php 5.3.8 ) and again started xampp_setup.bat as run as administrator (after copying my old htdocs and complete mysql folder) still that message comes Sorry... can't find php cli! must abort process press any key to continue...

more strange there is no error logs in apache\logs (blank folder) and searched all the new xampp folder didn't find any logs

any hint can help?

Re: recover xampp directory from raw-data backup to new PC

PostPosted: 19. October 2017 01:54
by itsme33
UPDATE:

well, after few hours of trying I copied the mysql and htdocs folder to the new version (1.7.7 xampp zip version) and it was saying same error.. then opened php.ini manually updated the paths then same thing in mysql/bin/my.ini manually updated the paths to the new location then run the xampp_setup.bat again as admin it gave error but ignored it kept pressing enter enter until gave me apache friends enjoy... now my databases seem ok and apache & mysql seem working.. I will keep testing and let you know if any new.

Thanks Altrea

Re: recover xampp directory from raw-data backup to new PC

PostPosted: 19. October 2017 05:15
by Altrea
The setup_xampp.bat script needs to be run with users rights, not with enhanced administrator rights.