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.

Upgrade EE 1.52 to 1.6 failed - Error 1069

July 07, 2007 9:11am

Subscribe [3]
  • #1 / Jul 07, 2007 9:11am

    qlas

    33 posts

    I’m used to upgrade EE and followed all the instructions.

    After navigating to update.php in my system folder via browser I got
    the following error message:

    ================

    Error: The following error was encountered
    MySQL ERROR:

    Error Number: 1069

    Description: Too many keys specified. Max 32 keys allowed

    Query: ALTER TABLE `exp_member_groups` ADD INDEX (`site_id`)

    ================

    Found this topic on the forum and followed Rick’s hint.

    But when I go to ...system/index.php I get another error message.

    ================

    MySQL ERROR:

    Error Number: 1054

    Description: Unknown column ‘site_id’ in ‘where clause’

    Query: SELECT weblog_id, blog_title FROM exp_weblogs WHERE site_id = ‘1’ AND is_user_blog = ‘n’ ORDER BY blog_title

    ================

    Can’t access ee CP any more.

    Please help.

    P.S.:
    - Used Last Build 1.6.0 20070705
    - cp_Themes upgraded with “classic” folder

  • #2 / Jul 07, 2007 1:19pm

    qlas

    33 posts

    Multiple Site Manager seems to fit my needs.
    As I understood, I have to upgrade first my ExpressionEngine 1.6. Pro install on mysite1
    Unfortunately I’m stuck with error upgrading to 1.6.

    I’ve to finish a project urgently before Monday. Are there any other solutions to this?
    May I upgrade another ExpressionEngine Pro install on mysite2, get and set up MSM,
    and import content, entries and posts from mysite1 to main EE install afterwards?

  • #3 / Jul 07, 2007 4:12pm

    qlas

    33 posts

    Dear Support Team,
    You’ve moved my pre-sales question here to join it to this thread.
    Nevertheless I think these are two different topics, even if they ar linked.

    1) First question tries to solve an upgrade problem
    2) Second question is more a feature question before buying MSM
    aims to understand, how MSM works.

    Maybe my second question was not clear enough:
    I’ve two websites: mysite1.com and mysite2.com working on two different domains
    with an EEpro install on each. Is it possible with MSM to fusion these two websites with all
    the entries and members to one and manage it from either of the two existing ee
    installs?

    Hope that anyone could answer to at least one of my questions?

  • #4 / Jul 07, 2007 4:32pm

    Sue Crocker

    26054 posts

    qlas, the upgrade problem has to do with something on your host’s side. Who are you hosting with?

    2. No, it is not possible to merge two different EE installs. You’d have to figure out who is one the site you’re going to have as the primary site.

    (Note: There really isn’t a primary site, but for our purposes it is.)

    You could run a query to create a .csv file with your members on the secondary site, and figure out which ones were duplicated, and make an import file to import those same members.

    The same thing with the posts. You could create an MT export, and use that to import in older entries.

    This is not a beginning user task. If you wanted to go that route, I’d contact someone on the Pro group, or post an add.

  • #5 / Jul 07, 2007 4:49pm

    qlas

    33 posts

    Thanks a lot for your first answer Sue,

    To start with my first question:

    the upgrade problem has to do with something on your host’s side. Who are you hosting with?

    a) My provider is ovh.com
    b) Hosting plan: 720plan (2nd most powerful shared hosting)
    Have been working with them for more than 10 years.
    Never had any ee upgrade or performance problems.

    - Might that be a temporary performance problem (did upgrade on Saturday)?
    - How could I roll back/do the upgrade again, given that part of the upgrade queries might have been processed?

    Need to be online again by Monday morning.
    Any help during weekend hours would be very much appreciated.

  • #6 / Jul 07, 2007 8:08pm

    Sue Crocker

    26054 posts

    Did you make a backup copy of your database before attempting to upgrade? What about your earlier config.php file?

    I’ve fixed botched installs manually by adding the tables myself using PHPMyAdmin.

  • #7 / Jul 07, 2007 8:59pm

    qlas

    33 posts

    Did you make a backup copy of your database before attempting to upgrade? What about your earlier config.php file?

    Yes, fortunately I have a db backup and a copy of earlier config.php.
    How should I proceed?

  • #8 / Jul 08, 2007 7:27am

    Sue Crocker

    26054 posts

    Just keep it handy. Send me FTP information, I’m going to need to go in and look around at the files you’ve uploaded. I’ll also need a SuperAdmin login and password to view the backend once I fix things.

    Please send the info to .(JavaScript must be enabled to view this email address)

  • #9 / Jul 08, 2007 8:33am

    qlas

    33 posts

    Dear Sue,
    Thank you so much. I’ve send you the data by email.
    If you could fix this I would be more than happy.

  • #10 / Jul 08, 2007 9:17am

    Sue Crocker

    26054 posts

    I sent you a message, I will need that original database dump after all.

  • #11 / Jul 08, 2007 9:52am

    qlas

    33 posts

    Thanks,
    I sent you the database dump.
    Hope that’s all you need for the moment.

  • #12 / Jul 09, 2007 8:04am

    Sue Crocker

    26054 posts

    qlas, I took your database dump and used it on one of my spare domains to see if I could get it to update over there. No joy.

    The thing is, I’ve updated several other sites on that server, and not run into that error message.

    About the only thing to do for now is to put the 1.5.2 files and database back up again on your server.

    I have a copy of the latest 1.5.2 release. That way you’d be up and running again.

    Your host might be able to help you get around the original problem.

    I’m sorry I wasn’t able to help any more with it. The other option is to start with a clean db and install 1.6. Then copy over your templates, entries, members and categories.

    The next step is up to you.

  • #13 / Jul 09, 2007 8:53am

    qlas

    33 posts

    About the only thing to do for now is to put the 1.5.2 files and database back up again on your server.
    I have a copy of the latest 1.5.2 release. That way you’d be up and running again.

    No luck. As I know the hosters tech support team our website will
    be offline now for another 48 hours.
    I’ll try first a rollback to 1.5.2. (I have left a copy on my hd.)

    Thank you very much Sue for your help anyway.

  • #14 / Jul 09, 2007 11:02am

    qlas

    33 posts

    As a first step I managed to reinstall my database dump on a local ee 1.52 install.
    Uuf.

    Have just a little problem now with “é, à, ö” etc. they show all up as “?” in the entry titels and body,
    whereas they show up right in the database vin phpmyAdmin.

    Default Character Set in Admin > General Config is set to utf-8 (as on the original install).
    Any hints on how to get the characters right after db-reimport?

  • #15 / Jul 09, 2007 12:09pm

    qlas

    33 posts

    :coolsmile: sigh of relief

    Roll back to 1.52 worked. With remote hosting provider characters show correctly after reimport.
    Everything seems to work fine again on http://www.linguaport.net/ee/

    Thread can be closed.
    Thanks.

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

ExpressionEngine News!

#eecms, #events, #releases