Thread

Please help.

This is the second upgrade attempt and I just got the same error as before.

A Database Error Occurred
Error Number: 1050

Table 'exp_snippets' already exists

CREATE TABLE `exp_snippets` ( `snippet_id` int(10) unsigned NOT NULL auto_increment, `site_id` int(4) NOT NULL, `snippet_name` varchar(75) NOT NULL, `snippet_contents` text NULL, PRIMARY KEY (`snippet_id`), KEY `site_id` (`site_id`) )

Filename: updates/ud_200.php

Line Number: 1428

I’ve followed the instructions to a T. I’ve started from a fresh database. I’ve even turned off saving templates as files in order to make this upgrade as smooth as possible.

We are installing in a dev directory, a dupe of our live site. We run 2 sites using multisite manager. I’ve tried everything I can think of to get this to work. I’ve made sure never to hit the back button. And thought for sure this attempt would work. Does anyone have any idea what is happening and how to fix it.

Edit: I’m running EE 1.7 and trying to upgrade to EE 2.2.1

Second Edit: Do I need to turn off all my 3rd party modules, extensions and plugins that won’t work with EE2? I was intending to upgrade these after I got EE 2 running.

aquaadmin,

Try following out tips relating to that specific error here

Make sure when you roll back to to 1.7 to try upgrade again that you restore the database into an empty database and not on top of the one currently there

Second Edit: Do I need to turn off all my 3rd party modules, extensions and plugins that won’t work with EE2? I was intending to upgrade these after I got EE 2 running.

The upgrade wizard will disable extensions for you. Upgrade the add-ons as soon as you have completed the EE upgrade though

We run 2 sites using multisite manager.

Take note of the specific instructions in pink relating to the MSM

let us know how you get on

Hi John,

Thanks for getting back to me but everything you suggested we’ve already done. Actually I am about to give up on EE 2 and just stick with 1.7 because I’ve wasted too much time trying to get this to work.

Let me tell you exactly what I have done, in a last ditch effort to get this to work, because at this point I’ve run out of ideas and am not sure what to do next.

We are currently running EE 1.7 with 2 separate websites using multisite manager, an external main site and our company internal site. The main site is in the root public_html directory and our internal site is in a folder within that directory, in compliance with how multi-site manager needs to be setup. In order to upgrade and not harm the live site, we had our web host, EngineHosting, duplicate our public_html directory into a dev_html directory. They set up a new database for us as well, by exporting the old database into a fresh new database.

Before I attempted to upgrade, I changed the config file in the system folder in the dev_html directory to point to the new dev database. Then I logged into the dev EE install and set up all the requisite configs to point to the dev_html directory. I intended to upgrade all of our add-ons after I made sure the EE 2 upgrade was successful and I could log into the control panel.

After assuring everything was ready I attempted the upgrade by following all the directions in the support docs. It failed and gave me the error 1050 as above.

So after doing so more research I decided it must be a problem with our saved template files. I reverted back to EE 1.7 and had EngineHosting set up a few more databases, just in case. According to them they exported the live database and imported it into 2 new databases (I have one more left). I reverted back to EE 1.7 and went through all the configs so that they would point to the dev_html directory. But this time I turned off all saved templates and in fact got rid of the basepath to the saved templates directory in the template settings so that no saved templates existed. I did all this for both sites.

I thought for sure this would do the trick but alas it failed again. Incidentally I did have problems trying to access the dev site of our internal website. We require a login to access this site, but each time we tried to login through the dev site it spit us back onto to the live site. We were unable to login to the dev site at all but decided we would tackle that after we upgraded.

So that brings me frustratingly to where we are right now. At this point I don’t know what else to do. Should I turnoff ALL modules, plugins and extensions? I went through and listed everything we have. Many are not compatible, which is fine because we are going to redesign the EE 2 site anyway and they may not be needed. I have upgrades for the others, but I figure we should get EE 2 running first and then handle the upgrades after I can get into the control panel at least. Plus it states in the directions that the upgrade installer will turn off all extensions anyway.

Below is a list of what add-ons we are using. Please let me know what I am doing wrong in terms of the upgrade. Actually at this point I wouldn’t be opposed to one of the EE tech support people handling the upgrade. I’d even consider paying someone to do this for us. We just have to move on with the redesign and upgrading EE is the first step. I’d rather build the new site on EE 2, because I’m sure EE 1.7 will be phased out, but if I can’t get this to work soon, EE 1.7 will be our only option.

Thanks for any help you can give me (us).

Add-ons for EE
Add-on (our version), author, upgrade version/issue

Modules,
Calendar (v.1.5.2),Solspace,1.6
Freeform (v. 3.1.0),Solspace,3.1.0
Shortcut (v. 1.1.1),Solspace,1.1.1
User (v. 2.0.8),Solspace,3.3.3

Plugins
Extract URL (v.1.0),http://www.chrisruzin.net/,discontinued
Flickr_tools (v.1.0),Solspace,discontinued
FLV Media Player Plugin (v.4.5.0),http://5pieces.com/addons/flv-media-player,unknown
Image Sizer (v.2.5.6),http://www.lumis.com/,discontinued
PHP Markdown Extra (v.1.2.4),http://www.michelf.com/projects/php-markdown/extra/,now called Smartdown
RepEEt (v.1.0.7),discontinued,now using Calendar

Extensions
Calendar Code Pack (v.1.0.0),Solspace,see Calendar Module
Calendar (v.1.5.2),Solspace,see Calendar Module
Checkbox (v.1.0.1),Mark Huot,discontinued
jQuery for the Control Panel (v.1.1.1),http://www.ngenworks.com/software/ee/cp_jquery/,unknown
Edit Remember (v.1.1.0),Mark Huot,discontinued
MD Dulee Noted (v.1.2.1),http://masugadesign.com/software/,not EE compatible
Multi Drop-down List (v.1.1.1) ,Mark Huot,discontinued
Shortcut (v.1.1.1),Solspace,see Shortcut Module
User (v.2.0.8),Solspace,see User Module

Just thought I check to see if anybody can help on this issue. Any takers? It seems like this should be something simple for EE tech support but I dunno. Any thoughts on this upgrade issue would be very appreciated!

Hi, aquaadmin -

Have you seen this troubleshooting article? It was written specifically against this problem.  There is also this new wiki entry on troubleshooting upgrade errors which might help you move forward.

Another thing we’ve found success with is simply disabling Javascript prior to running the update.  That avoids the JS itself looping during the upgrade process.

Does anything in there help you move forward?

Thank you!