Support

The backup operation has been halted because an error was detected.
The last error message was:

AJAX Loading Error
HTTP Status: 500 (Internal Server Error)
Internal status: error
XHR ReadyState: 4
Raw server response:
Internal Server Error

The server encountered an internal error or misconfiguration and was unable to complete your request.

Please contact the server administrator, [email protected] and inform them of the time the error occurred, and anything you might have done that may have caused the error.

More information about this error may be available in the server error log.

Additionally, a 404 Not Found error was encountered while trying to use an ErrorDocument to handle the request.
----------------------------------------------------
here is the last few lines from log:
INFO |100611 10:31:06|Scanning directories of /language
INFO |100611 10:31:06|Scanning files of /language
DEBUG |100611 10:31:06|Packing files
DEBUG |100611 10:31:06|-- Adding language/.com_jashowcase.ini to archive (source: /language/.com_jashowcase.ini)
DEBUG |100611 10:31:06|-- Adding language/index.html to archive (source: /language/index.html)
INFO |100611 10:31:06|Scanning directories of /language/pdf_fonts
INFO |100611 10:31:06|Scanning files of /language/pdf_fonts
DEBUG |100611 10:31:06|Packing files
DEBUG |100611 10:31:06|-- Adding language/pdf_fonts/droidsansfallback.z to archive (source: /language/pdf_fonts/droidsansfallback.z)
DEBUG |100611 12:39:25|Kettenrad :: Attempting to load from database
DEBUG |100611 12:39:25| -- Loaded stored Akeeba Factory
DEBUG |100611 12:40:00|Kettenrad :: Attempting to load from database
--- END OF RAW LOG ---

In this case, the 404 error is not important, it is the 500 error that is the problem. The 500 error is designed not to tell you why it occurred. There would be more information about it in the server error log.

One of the things that will cause this is exceeding the host file size limit. Go to the Akeeba Configuration screen and click the Configure link on the Archiver Engine line. Now drag the Part size for split archives slider to 2 Mb. You can get it close by dragging, then fine tune it with the arrow keys. Save and retry your backup.

yes, that fixed the error. thanks

Great! You can check with your host to find out exactly what the file size limit is, then set the split size accordingly. It is worth the support ticket because if the maximum is actually above 2 Mb, you can reduce the number of parts in your backup. You can also just experiment, increasing the part size until it fails again. It works, you don't have to fine tune it at all. :)