ExpressionEngine CMS
Open, Free, Amazing

Thread

This is an archived forum and the content is probably no longer relevant, but is provided here for posterity.

The active forums are here.

"Patch unsuccessful!" - 2.3.1 upgrade

November 04, 2011 10:46am

Subscribe [3]
  • #1 / Nov 04, 2011 10:46am

    Morten Norli

    3 posts

    Hi,
    I see this has been up for discussion a couple of times. I have the same problem, but I can’t really say I did anything out of the ordinary or not according to the updating guidelines. I have successfully updated 6 other websites, and did it all in exactly the same way.
    On the seventh, however, the control panel shows this error message:

    Patch unsuccessful!
    This patch cannot be applied to ExpressionEngine versions older than 2.3.0.
    Please do a full upgrade to version 2.3.1 or contact tech support for more information.

    I’ve tried to run the update again, but when I start the update via the admin.php page I get another error message right after I’ve agreed to the terms and conditions:

    A Database Error Occurred
    Error Number: 1060
    Duplicate column name ‘batch_location’
    ALTER TABLE `exp_upload_prefs` ADD `batch_location` VARCHAR(255)
    Filename: updates/ud_215.php
    Line Number: 169

    The website seems to be running as it should, but for obvious reasons I’d like to update it to the latest release. I’m upgrading from 2.1.3. Where do I go from here?

    Best regards,
    /Morten

  • #2 / Nov 06, 2011 1:49pm

    Sean C. Smith

    3818 posts

    Morten,

    Welcome to the forums. glad to hear you had the first six upgrades go well. Let’s get busy troubleshooting this latest one.

    The reason you’re getting the database error after the second attempt is because during the first upgrade attempt some of the database changes were completed - this means the second time around you’re going to end up with duplicate tables.

    On this Wiki Page it states that after a failed update you should wipe your database empty (drop all tables) and then restore from the database backup you made before proceeding with the initial upgrade.

    Could you please do that. and retry your upgrade from your current version to 2.3.1 after restoring to your working database.

  • #3 / Nov 07, 2011 2:08am

    Morten Norli

    3 posts

    Hi Sean, and thanx for getting back to me. Uhm - I was afraid you would ask about the database backup… I managed to delete it, before I realized that the update wasn’t successful. Stupid, I know - but I’m being sent back to the “structure” module every time I “do something” on this website, so I didn’t really see the error message in the CP before I deleted the backup. So, do we have another approach - or do I wait for 2.3.2…?

    Best regards,
    /Morten

  • #4 / Nov 08, 2011 6:45pm

    Robin Sowell

    13255 posts

    Ah- 2.3.2 won’t really help you out.  We just need to figure out where things went pair shaped and then go from there.

    If you look at your config file (system/expressionengine/config/config.php) what’s it show for your version number?  And do you have a config variable called ud_next_step- and if so, what’s it’s value.

    We’ll just track down where things stalled out and manually bulldoze past it, so no worries.

  • #5 / Nov 09, 2011 10:53am

    Morten Norli

    3 posts

    Thanx, Robin - but I figured it out, so I’m good…

    Cheers,
    /M

  • #6 / Nov 09, 2011 11:08am

    Robin Sowell

    13255 posts

    Woot!  If you do run into any trouble with it?  Just start up a new thread and we’ll work it through!

.(JavaScript must be enabled to view this email address)

ExpressionEngine News!

#eecms, #events, #releases