Thread

Hi Omkar,

Just to clarify, the only error you see is the browser confirmation dialogue that says, “The update script failed without returning an error.  Please contact tech-support,” correct? If that’s the case, this appears to be an AJAX error, so my recommendation is to take AJAX out of the loop here. After restoring your backup and ensuring that you wipe your database before importing the database backup, please try the upgrade again with JavaScript disabled on your browser.

Also, as a precaution against some strangeness we’ve seen with using Firefox to upgrade EE, make sure you’re using Safari or Chrome instead.

If you get any errors this time around, document them here and we’ll go from there.

Hi Kevin,

Yes, that is the error that I am getting.  I tried your suggestion to turn off Javascript and use Chrome and it still failed.  This time, I get:

Server error
The website encountered an error while retrieving <a href="http://myserver/system/index.php?C=wizard&M=do_update&agree=yes&language=english">http://myserver/system/index.php?C=wizard&M=do_update&agree=yes&language=english</a>. It may be down for maintenance or configured incorrectly.

Thanks for the update, Omkar. At this point, we’re going to work with you privately on this. We’ll post public updates here as we’re able to do so.

Just updating the thread to let onlookers know that Omkar was recently able to upgrade his site to EE 2.3.1 using the new alternative upgrade option for large DBs, an upgrade path that automatically presents itself if your database is too large to be upgraded through the browser.