Thread

We are attempting (finally) to upgrade from 2.something to the latest version and the upgrade seems to run fine for about 10 minutes and then I get the following error:

Network Error (tcp_error)

A communication error occurred: “”
The Web Server may be down, too busy, or experiencing other problems preventing it from responding to requests. You may wish to try again at a later time.

For assistance, contact your network support team.

Your request was categorized by Blue Coat Web Filter as ‘Real Estate’.
If you wish to question or dispute this result, please click here.

—-

This is the second time we’re attempting this and I’ve had to have the previous version restored from backup.  Can someone give me a hint as to what might be causing this issue? I know I followed the directions at http://ellislab.com/expressionengine/user-guide/installation/update.html to the letter!

This is very frustrating and I’d like to get it resolved.

Thanks

Hey JavaMan,

I am sorry to hear you are running into this problem.

This is 100% server related. And I can almost guarantee it’s Blue Coat. Please work with your server admin and wither check the logs for more direction on how to resolve this or take Blue Coat out of the picture while you install.

I have a feeling you are doing everything right, but the server is not playing nice.

Cheers,

Ok, so I’m working from home today to try to upgrade this outside of the proxy/firewall.  SO it seemed to be going just fiine this morning until:

A Database Error Occurred

Error Number: 1050

Table ‘exp_comment_subscriptions’ already exists

CREATE TABLE `exp_comment_subscriptions` ( `subscription_id` int(10) UNSIGNED AUTO_INCREMENT, `entry_id` int(10) UNSIGNED, `member_id` int(10) DEFAULT ‘0’, `email` varchar(50), `subscription_date` varchar(10), `notification_sent` char(1) DEFAULT ‘n’, `hash` varchar(15), PRIMARY KEY `subscription_id` (`subscription_id`), KEY `entry_id` (`entry_id`), KEY `member_id` (`member_id`) ) DEFAULT CHARACTER SET utf8 COLLATE utf8_general_ci;

Filename: updates/ud_211.php

Line Number: 101

With a “Back” link. If the table exists, why doesn’t it simply verify that it’s config’d right (right columns,etc…)? 

More importantly, how can I get around this?

Sorry, can’t help, but want to chime in. I got these same database errors on trying to upgrade. So I aborted the upgrade and now everyone in my company is locked out of EE—despite my having reinstalled the backup database and files.

I’ll be interested to hear if you get a response on why you got this error, and if you have any trouble if you try to reinstall the old files.

You can see the thread for my support issue under “Aborted upgrade Now can’t log into EE”

Good luck!

I have had no problem getting into the CP -at least so far.  And I haven’t done anything other than restore the code/folders that were backed up.  The DB has remained where it is and seems to be working just fine (and I’ve pounded on it a bit)

I just know I need to get past this error.  I would think that the upgrade would check if the table existed first, and not attempted to create it,but update it (if needed), and proceed on.

Now I’m stuck until I can get past this.

Hey JavaMan,

It sounds like the previous upgrade left some “artifacts”.

Please follow this guide for retrying after a failed update.

Note that you must drop all the tables to avoid running into another duplicate message.

Please let me know how it goes.

Cheers,

Ok now we’re having this same issue but the above steps did not help.  I literally can’t upgrade to 2.5.2.  My error is the same even after wiping out the failed install db and uploading our backed up DB.  We are on EngineHosting for our server.

A Database Error Occurred

Error Number: 1050

Table 'exp_comment_subscriptions' already exists

CREATE TABLE `exp_comment_subscriptions` ( `subscription_id` int(10) UNSIGNED AUTO_INCREMENT, `entry_id` int(10) UNSIGNED, `member_id` int(10) DEFAULT '0', `email` varchar(50), `subscription_date` varchar(10), `notification_sent` char(1) DEFAULT 'n', `hash` varchar(15), PRIMARY KEY `subscription_id` (`subscription_id`), KEY `entry_id` (`entry_id`), KEY `member_id` (`member_id`) ) DEFAULT CHARACTER SET utf8 COLLATE utf8_general_ci;

Filename: updates/ud_211.php

Line Number: 101

*bump* hopefully someone can escalate this issue on Monday I realize you guys are busy but we are locked out of our system until we can get this resolved.  Thanks!

Hey design132,

Did you drop all the tables before starting? It still sounds like the DB is not totally clean.

Are you upgrading directly to 2.5.2 or are you upgrading to major revisions? I ask because there is a know bug in an earlier version where not having the comments module installed would throw this error.

Can you tell me the version you are currently on? Is it before 2.4?

Thank you,

Actually.. 
“We have detected that you are currently running ExpressionEngine version 2.1.0”

When I go to remove the database, I completely drop all tables, then I reload the DB.  Could this be what’s causing it?  If I can’t reload the database then what would we do with all our data?

Any ideas guys?  We really need to get into our site asap.  Thanks.

Hello design132,

Check out this guide which walks you through a failed upgrade. Please take note of the following line.

So before you attempt another upgrade, completely wipe your existing database clean. If it’s possible, delete the database itself and create a new, empty database. Then restore your database from backup, and try the upgrade again.

I think this will get you back in business.

Cheers,

I’ve been doing this, even in previous steps.

1) completely delete all files inside the database so there are 0 tables/fields.
2) reload the database from the backup we made.
3) run the upgrad utility.
4)

We have detected that you are currently running ExpressionEngine version 2.1.0

If you are ready to update ExpressionEngine to version 2.5.2 click the link below:

Click here to update ExpressionEngine to Version 2.5.2

5) Agree to the license Agreement
6)

A Database Error Occurred

Error Number: 1050

Table ‘exp_comment_subscriptions’ already exists

CREATE TABLE `exp_comment_subscriptions` ( `subscription_id` int(10) UNSIGNED AUTO_INCREMENT, `entry_id` int(10) UNSIGNED, `member_id` int(10) DEFAULT ‘0’, `email` varchar(50), `subscription_date` varchar(10), `notification_sent` char(1) DEFAULT ‘n’, `hash` varchar(15), PRIMARY KEY `subscription_id` (`subscription_id`), KEY `entry_id` (`entry_id`), KEY `member_id` (`member_id`) ) DEFAULT CHARACTER SET utf8 COLLATE utf8_general_ci;

Filename: updates/ud_211.php

Line Number: 101

« Back

Hey design132,

Hmmm ... not good.

Is the database you are loading in a working version or is it a back you took after a failed upgrade? That would make sense. Then you are loading in a DB with “fragments” as well call them.

If that is not the case, please let me know and we can go from there.

Thank you,

Well it took me all day but I was able to obtain a database backup from enginehosting absolutely prior to our upgrade fail and it’s giving me the same error.