Thread

I’m currently working on upgrading our long-standing 1.7.3 installation to 2.7.3, staged on a new development server. The 1.7.3 code and databases have been moved over fine and are working as expected on that version, but whenever I run through the 2.7.3 upgrade script, I’m getting the dreaded “The update script failed without returning an error.  Contact Tech Support” message, which is of course rather unhelpful.

I’ve checked, repaired, and optimized all database tables, and have now been through the process several times with the same results, which always occurs in a slightly different place, during the initial 2.0 checks for DST discrepancies, where the system appears to be building the update.sh script. Config.php shows the next step as “large_db_check.”

I’m not receiving any memory errors, although PHP memory_limit is only set to 96M—the same value that we’ve been running on our production site. I don’t have direct control over this value; although I’m sure I can ask my hosting provider to increase it, I figured I’d check here first, as I’ve seen reports from others with higher limits having the same problem, so I’m not entirely sure that’s it either.

Any other suggestions would be helpful. I’ve been trying to trace this down myself, but without any error logs or any sign of where the process is failing, I’m pretty much at a complete loss.

I finally solved this particularly problem, so just to close the loop…

While I never tracked down the original cause, I basically managed to force the database to upgrade successfully by increasing the PHP memory limit to 512M and then editing the ud_200.php script to skip the “large db upgrade” stage—effectively letting the script handle the database conversions directly, which it was able to do successfully with the higher PHP memory limit.

Note that the largest individual databases were around 150MB, and for whatever reason the existing databases were already in UTF-8 rather than LATIN-1, so that might have had something to do with it as well.