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.

Failed upgrade from 2.1.3 to 2.4 - Blank screen

February 19, 2012 5:00pm

Subscribe [2]
  • #1 / Feb 19, 2012 5:00pm

    360esoft

    8 posts

    Hi,
    I am trying to upgrade from 2.1.3 to 2.4.
    I’ve got backups to roll back if necessary, and it seems that I may have to do that.
    So when I clicked “upgrade”, I saw the progress going, but it stopped at 2.2 and then the screen went blank. The page source is also blank, and in the console there’s a javascript error: “Uncaught Error: “create” can only be used in extension processes. See the content scripts documentation for more details.”
    I’ve been waiting to see if anything might happen, but no luck. I’m trying to update with Chrome 17.0.963.56 m. My server is a Windows IIS.

    On a new tab, I reopened admin.php: it tells me “welcome to the upgrade wizard”, and also detects that I’m now running EE 2.2.0 instead of 2.1.3.
    Anyone encountered such issue? Any clues to what’s going on?
    Should I try the update process again?

    Thanks in advance!

  • #2 / Feb 20, 2012 8:49am

    360esoft

    8 posts

    Any ideas?

  • #3 / Feb 20, 2012 3:22pm

    Dan Decker

    7338 posts

    Hi 360esoft,

    I’m sorry you ran into trouble with the update process!

    The only errors you report are in the JavaScript debug console?

    The safest route is to roll back and try the update again. You may even consider trying in Firefox.

    Be sure to read the Wiki entry on “Retrying After a Failed Upgrade”.

    Let me know if the process doesn’t complete after the next attempt.

    Cheers,

  • #4 / Feb 27, 2012 3:25pm

    360esoft

    8 posts

    hi,
    it took some time before I tried to upgrade again, but here I am, and it failed once more.
    I restored my previous database and restored the config file, and encountered this error:

    {"error":"
    
    Error Number: 1060<\/p>\n\n
    
    Duplicate column name 'batch_location'<\/p>\n\n
    
    ALTER TABLE `exp_upload_prefs` ADD \n\t`batch_location` VARCHAR(255)<\/p>\n\n
    
    Filename: ...\\codeigniter\\system\\database\\DB_driver.php<\/p>\n\n
    
    Line Number: 330<\/p>"}

    Any help is appreciated!
    Meanwhile, I’ll look for similar issues on the forum.

  • #5 / Feb 27, 2012 4:39pm

    360esoft

    8 posts

    So I was looking around in the forum to see what people did when they encountered a 1060 error.
    I followed this thread and dropped the tables that could have caused errors in duplication.
    The thing is, updating from 2.1.3, some tables did not exist yet…
    I dropped the following:
    TABLES
    exp_file_watermarks
    exp_files
    exp_file_categories
    exp_file_dimensions
    exp_category_groups => only exclude_group column
    exp_upload_prefs => only batch_locations and cat_group columns

    And now, when trying to update again, it says:

    {"error":"
    
    Error Number: 1005<\/p>\n\n
    
    Can't create table '360_ee_db.exp_file_watermarks' (errno: 121)<\/p>\n\n
    
    CREATE TABLE `exp_file_watermarks` (\n\t`wm_id` int(4) UNSIGNED AUTO_INCREMENT,\n\t`wm_name` varchar(80),\n\t`wm_type` varchar(10) DEFAULT 
    'text',\n\t`wm_image_path` varchar(100),\n\t`wm_test_image_path` varchar(100),\n\t`wm_use_font` char(1) DEFAULT 'y',\n\t`wm_font` 
    varchar(30),\n\t`wm_font_size` int(3) UNSIGNED,\n\t`wm_text` 
    varchar(100),\n\t`wm_vrt_alignment` varchar(10) DEFAULT 'top',\n\t`wm_hor_alignment` 
    varchar(10) DEFAULT 'left',\n\t`wm_padding` int(3) UNSIGNED,\n\t`wm_opacity` int(3) 
    UNSIGNED,\n\t`wm_x_offset` int(4) UNSIGNED,\n\t`wm_y_offset` int(4) 
    UNSIGNED,\n\t`wm_x_transp` int(4),\n\t`wm_y_transp` int(4),\n\t`wm_font_color` 
    varchar(7),\n\t`wm_use_drop_shadow` char(1) DEFAULT 'y',\n\t`wm_shadow_distance` int(3)
    UNSIGNED,\n\t`wm_shadow_color` varchar(7),\n\tPRIMARY KEY `wm_id` (`wm_id`)\n) DEFAULT 
    CHARACTER SET utf8 COLLATE utf8_general_ci;<\/p>\n\n
    
    Filename: ...\\codeigniter\\system\\database\\DB_driver.php<\/p>\n\n
    
    Line Number: 330<\/p>"}

    Continuing to investigate.

  • #6 / Feb 27, 2012 8:04pm

    Sean C. Smith

    3818 posts

    Hi 360esoft,

    It looks to me like you have artifacts left in your database from a failed upgrade. Please read this article on retrying after a failed up grade. The key here is to completely drop your database before restoring your backup.

    Please do that and then let me know how it goes.

    Sean

  • #7 / Feb 28, 2012 9:49am

    360esoft

    8 posts

    Someone else is taking care of the database. I asked him to wipe it out, restore the last working backup, I replaced my config file by the original (before trying to upgrade), and I ended up with the same results as my first post in this thread: stopped at 2.2, blank page, but no Javascript error.
    This time I tried on Firefox 10.0.2

  • #8 / Feb 28, 2012 2:17pm

    360esoft

    8 posts

    This has already gone on 2nd page.
    I tried again, wiping out my database again, restored the previous config.php file, and it seems to have completed 2.2.0 update. But then it stops again.
    Following the upgrade troubleshooting guide, here is what I conclude:
    - I ran the wizard server before trying to upgrade and again today, just to make sure. My IIS server is ok, all required elements are there. URL Segment Support is not working, but that has not been an issue previously.
    - Retrying after a failed upgrade: I have wiped out the entire database 2-3 times now, with the same result, stopping at 2.2.0, as it happened the 1st time.
    - Third party modifications: I made a fresh install of EE 2.4 on a sandbox server a few weeks ago, and the following add-ons work correctly: Matrix, Biber Multi-Language, Developer, ed_imageresizer, freeform, low nice date, NSM better meta, Wygwam. Need to verify these: Reelocate, Word limit,  Bridge, Detour.
    - Multiple Browser requests: I have tried both in Chrome and Firefox. Both upgrade processes failed.
    - MySQL errors: I don’t even know if there are errors, the screen is blank after 2.2.0.
    - Config file issues: I don’t have custom variables.

    I don’t know what to investigate. If at least I could have an error message of some sort, that would help. Anyone has an idea, or can refer me to a forum thread that resembles my case?

    Thanks,

  • #9 / Feb 29, 2012 2:12pm

    Dan Decker

    7338 posts

    Hi 360esoft,

    I understand your frustration and I’m going to do everything I can to get you through this process. When it comes to stalled/failed updates, wash-rinse-repeat is an arduous process, but it is the way to get passed this.

    Are you attempting the update on a live server or do you have this running in a test environment?

    At this point, you should set up a local or development server to work through the update process first. Let’s get the kinks worked out. Then you will have a documented process for performing the update on the live server.

    You can set up a local/dev copy of your server by following the steps for Moving ExpressionEngine to Another Server.

    Once you have that up and running, try the update there. If it stalls at the same place, go immediately an look at /system/expressionengine/config/config.php and tell me what the contents are?

    Cheers,

  • #10 / Feb 29, 2012 2:41pm

    360esoft

    8 posts

    Thanks for your reply, Dan.
    I will keep you posted on what is happening. Right now, other non-web concerns are prioritized, so I have to push back the update to next week. I will for sure follow your advice.
    Thanks!

  • #11 / Mar 01, 2012 4:55pm

    Dan Decker

    7338 posts

    Hi 360esoft,

    For the time being, I’m going to close this. When you get ready to try again, start a new thread and we’ll be here to help you along!

    Cheers!

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

ExpressionEngine News!

#eecms, #events, #releases