Support

Akeeba Backup for Joomla!

#8510 invalid ajax data received -

Posted in ‘Akeeba Backup for Joomla! 4 & 5’
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

Joomla! version
n/a
PHP version
n/a
Akeeba Backup version
n/a

Latest post by nicholas on Tuesday, 22 February 2011 15:33 CST

user11441
com akeeba 3.0 pro.

When I try to restore with Kickstart, I get this error:
Invalid AJAX data received:
NULL Invalid archive type or extension

I have attached my log.TEXT

dlb
There are a couple of rough spots on kickstart 3.0, please use the Developer's Release.


Dale L. Brackin
Support Specialist


us.gifEnglish: native


Please keep in mind my timezone and cultural differences when reading my replies. Thank you!


????
My time zone is EST (UTC -5) (click here to see my current time in Philadelphia, PA)

user11441
OK. I tried the new kickstart, still didn't work. It said it could not open a file.

I have now tried Akeeba (professional) 4 times on 3 different servers, and it has not worked perfectly any of the times, and kickstart has never worked. So, either it doesn't work, or I am just not understanding it.

For this site, I gave up trying to use kickstart, and downloaded and then uploaded the backup file with ftp set on binary, unzipped the backup file by hand, created a new database and went thru the install process. however, none of the css, template or images are visible. I have attached a screen shot. It is supposed to look like www.petdiapers.com

But, it looks like this:

nicholas
Akeeba Staff
Manager
Did you follow the troubleshooting steps in Finalizing the restoration process documentation section? You may also need to update $live_site as outlined in this part of Joomla!'s documentation. Even though it refers to SEF URLs, believe me when I say that it also affects the way CSS and images may be loaded. Been there, more than once! :)

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!

user11441
I checked the articles you posted. The .htaccess file seems fine, and is still labeled .htaccess.

I tried to check the SEF settings, but when i tried to login to the backend of the new Joomla, I got this error:
404 - Component not found

You may not be able to visit this page because of:

1. an out-of-date bookmark/favourite
2. a search engine that has an out-of-date listing for this site
3. a mistyped address
4. you have no access to this page
5. The requested resource was not found.
6. An error has occurred while processing your request.

Please try one of the following pages:

* Home Page

If difficulties persist, please contact the System Administrator of this site.

Component not found

nicholas
Akeeba Staff
Manager
This looks like a partial restoration, i.e. not all of your files have been restored. Please follow the following steps:
1. re-download your backup archive from your original server using FTP in Binary transfer mode. This will rule out any corrupt downloads. Do note that if you are using split archives, you'll need to download all of the backup parts (.jpa, .j01, ... or .zip, .z01, ...) for the extraction to work properly.
2. Re-upload the backup archive to the new server using FTP in Binary mode, for the same reasons.
3. Run the restoration again, using Kickstart. Alternatively to steps 2 & 3, you can extract the archive locally (using Akeeba eXtract Wizard) and upload all of the extracted by FTP, overwritting existing files. Then run the installation by pointing your browser to http://www.yournewsite.com/installation/index.php

This should make sure that all of the files are in there and the login issue shouldn't happen at the restored site.

If the problem persists, please check if you have any component which is running at login time which might be throwing this error. So far I haven't found any such component, but I can never be 100% certain that there really is no component 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!

user11441
Rebacked up site. Downloaded, then uploaded using ftp on binary. Ran Kickstart svn174, Got this error:

Could not open /var/www/vhosts/petdiapers.com/httpdocs/installation/css/img/busy.gif for writing.

The server says there is 9.7GB free and my backup file is 53288KB.

When I tried to extract on my computer using Akeeba extract wizard, I get the error:
"The archive file is corrupt, truncated or archive parts are missing"

dlb
The kickstart error is a permissions problem, please try kickstart's ftp mode. It is much better at setting permissions than the direct writes mode. This may also be a problem with the permissions in the root folder of your site, kickstart uses that as a temporary folder. You can create a temporary folder, give it 777 permissions, and add it to the end of the temporary folder path in the ftp setup screen.

What version of eXtrct are you using?


Dale L. Brackin
Support Specialist


us.gifEnglish: native


Please keep in mind my timezone and cultural differences when reading my replies. Thank you!


????
My time zone is EST (UTC -5) (click here to see my current time in Philadelphia, PA)

user11441
Trying your suggestions.

Akeeba extract is:
Akeeba eXtract Wizard.msi

I tried it again using the jpa format instead of .zip and it did extract on my computer. But, uploading to the server is taking hours. Is there any way to use the extract wizard on the server?

user11441
Dale,
I have tried Kickstart in the ftp mode and created a temp folder with 777 permission. The Kickstart says that the temp file is writable when I check, but then when I click "test ftp connection", it does not find the temp file. Here are screen shots of the errors, and the filezilla screen, where you can see where the temp folder is.



dlb
I can't read the screen shots well enough to tell you exactly what to put in the temp folder, but it should be the contents of the ftp path from the field above+/temp. Kickstart is acting as an ftp client, so it needs the whole ftp path to the temp folder. You were on the right track figuring it out from FileZilla. :)


Dale L. Brackin
Support Specialist


us.gifEnglish: native


Please keep in mind my timezone and cultural differences when reading my replies. Thank you!


????
My time zone is EST (UTC -5) (click here to see my current time in Philadelphia, PA)

user11441
That's why I sent the screenshots. I feel that we did everything that you suggested.
the folder that got accepted as the root folder was /httpdocs
I created a /httpdocs/temp with 777
I tried everything I could think of in the temp folder location

temp
/temp/
temp/
/httpdocs/temp (what the filezilla window shows
/httpdocs/temp/

There is no combination that works. I've tried everything -- now I've unzipped locally and uploaded and I'll have to start again with another site -- but there is definately something wrong here -- I can give you access if necessary.

user11441
Nicholas said :
"Alternatively to steps 2 & 3, you can extract the archive locally (using Akeeba eXtract Wizard) and upload all of the extracted by FTP, overwritting existing files. Then run the installation by pointing your browser to http://www.yournewsite.com/installation/index.php "

I just did this exactly. Uploaded and went through the installation process. When I tried to login, I get the same errors:
404 - Component not found

You may not be able to visit this page because of:

1. an out-of-date bookmark/favourite
2. a search engine that has an out-of-date listing for this site
3. a mistyped address
4. you have no access to this page
5. The requested resource was not found.
6. An error has occurred while processing your request.

Please try one of the following pages:

* Home Page

If difficulties persist, please contact the System Administrator of this site.

Component not found


I have no extra components in the site. This took hours!

dlb
Could you please post your backup log again, the one in the original post appears to be gone. I want to double check what went into the archive.


Dale L. Brackin
Support Specialist


us.gifEnglish: native


Please keep in mind my timezone and cultural differences when reading my replies. Thank you!


????
My time zone is EST (UTC -5) (click here to see my current time in Philadelphia, PA)

user11441
Here is the most recent backup log.

##text##

dlb
Obviously looking for something missing from the log is not an exact science. Both the /components and /administrator/components folders have some files and folders being backed up, so the entire tree is not being skipped. There are no errors or warnings in the log, no obvious configuration errors. Without knowing what component is missing, there isn't anything more the log can tell us.

Do you have access to the server error log on the sever that this site is located on? That may give us more information about what is missing.


Dale L. Brackin
Support Specialist


us.gifEnglish: native


Please keep in mind my timezone and cultural differences when reading my replies. Thank you!


????
My time zone is EST (UTC -5) (click here to see my current time in Philadelphia, PA)

nicholas
Akeeba Staff
Manager
As far as I can see, the com_login back-end component (the one which displays the administrator login form) is being backed up. At this point, I have to ask: are you installing on a subdirectory or a subdomain? If so, did you follow the documentation's instructions for post-restoration problems? Also, what is the URL you see on your browser when you receive the error message? Is it a URL in the new site you have just restored?

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!

user11441
Dale,

Attached is the server error log from my most recent attemp. First I tried and failed to use Kickstart, then uploaded the zip file, unzipped it on the server and then installed from there.

##text##

dlb
I don't speak "Error" so I don't know what is going on, but there are kickstart related errors in there. Nicholas will know what they mean.


Dale L. Brackin
Support Specialist


us.gifEnglish: native


Please keep in mind my timezone and cultural differences when reading my replies. Thank you!


????
My time zone is EST (UTC -5) (click here to see my current time in Philadelphia, PA)

nicholas
Akeeba Staff
Manager
Did you just follow the advice I linked you to on my previous post? I am 99.9% convinced that this is a problem with .htaccess. The RewriteBase in your case should be /, i.e.:
RewriteBase /

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!

user11441
Nicholas,
Yes, I tried your suggestion. The instructions said that the .htaccess would have been renamed to htaccess.bak, but it was not, it was still .htacces. There was a line in the file that read:
# RewriteBase /
which I changed to read:
RewriteBase /

I assume this is what you mean? Making this change in the .htacess didn't make any difference.

Also, when I log in and get the 404 error, you are right , and the url is weird:
http://pet-diapers.com/administrator/www.pet-diapers.com/administrator/index.php

So, somehow, something is pointing to the wrong place. However, I did not install it in a subdirectory, but in httpdocs, which is the root. But, what am I doing wrong here?

Thanks.

nicholas
Akeeba Staff
Manager
The .htaccess file is renamed to htaccess.bak during Kickstart's run to avoid conflicts throughout the restoration process. When you click on Clean Up it is renamed back to .htaccess, as per the documentation. This is the normal and intended behaviour.

Now, your server screws up the URL and I am not sure why. Check if you have an php.ini files in your site's root and/or the administrator directory. If so, rename them to php.ini.bak. Also try renaming your .htaccess file(s) is your site's root and/or the administrator directory to htaccess.bak to see if it helps.

If none of this works, you'll have to file a support ticket with your host because the matter will be beyond what we can do to fix it from the end user's end (it will require some intimate knowledge of the exact server setup to produce a viable solution).

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!

user31273
invalid ajax data received
i did everyb thing required to transfer my local web pages( that were backed up by akeeba backup) to a server and stacked with this notorious error. and this occurred in the mid way of extraction.it advances fine then error e.t.c.
please help? this is the same error that is outlined by previous posters on this site.
any help is really appreciated
thank you!!!

i tried to rename to .htaccess.back it goes half way and stopped with that error.there was some good sign.any ways ended up in error

user31273
Fatal error: Cannot make non static method JApplication::getRouter() static in class JSite in /home/a7575903/public_html/includes/application.php on line 606

after performing what you said suceeded to extract but at the end ocurred the above error
"
"Fatal error: Cannot make non static method JApplication::getRouter() static in class JSite in /home/a7575903/public_html/includes/application.php on line 606


would you solve this for me!! a7575903 is my user name so disregard this
thank you

nicholas
Akeeba Staff
Manager
This error comes from the Joomla! core itself. Are you trying to restore to a host running PHP 5.3? Please note that PHP 5.3.3 and later do not allow Joomla! to function properly. PHP 5.3.0 and later do not allow most Joomla! third party extensions (including templates) to function properly. In both cases, such fatal errors can occur and the only workaround is to use a lower PHP version.

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!

user31273
thank you v.much for devoting your time.i did not ever thought that as a cuase.my assumtion was due to transfering joomla1.5 webpages on to joomla1.6.
i let you know whenever something gets fixed

thank you!!!!

nicholas
Akeeba Staff
Manager
So, you tried to restore the backup of a Joomla! 1.5 site on another Joomla! 1.6 site?

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!

user31273
yes i tried joomla 1.5 site extracted on joomla 1.6 which is on the hosting server.firstly i didnot released that there were a verstion difference at all.the backup was extracted correctly and the database profiles were changed on the way of extraction
and that was beautifully carried out.installation files were removed by quickstart extractor -then thethank you message for your confidence on this akeeba tool-then you expect to see the web page you see that fatal error message.even i donot know how to upgrade.so i am currently left with a lot of work to dig.
i dropped off j-1.5 and am working on j-1.6

thank you

nicholas
Akeeba Staff
Manager
OK. What you try isn't going to work because Joomla! 1.5 and Joomla! 1.6 are very different. You can't restore one on top of the other without all hell breaking loose. You have to start with a clean slate. Begin by removing all files, folders and database tables. Then, restore the Joomla! 1.5 site from the backup on the now empty hosting space. If this doesn't work, please tell us exactly which problems you encountered so that we can help you get past them.

Once you have the Joomla! 1.5 site up and running, you can attempt to migrate most of your website's content to a clean Joomla! 1.6 site. The best (and only!) way to do that is to use Matias Aguirre's jUpgrade component.

WARNING: Your mileage may vary! If you are using third party extensions (components, modules, plugins, templates) which are not compatible with Joomla! 1.6, you will probably end up with a half broken web-site. Just for the record, I have not attempted to migrate any website to Joomla! 1.6 yet, mostly because many of the extensions I am using on my sites are not yet Joomla! 1.6 ready. You are entering uncharted territory. Be brave and proceed with caution. There might be a few dragons to slay and a few canyons to cross without a bridge, but it's worth the trouble :)

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!

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!