Does that help?
Yes! Thank you Sue!
can you check PHP Info for your max execution time and let us know that that value is?
max_execution_time is 300 local, 300 master.
PHP Version 5.2.11.
Please advise.
This is an archived forum and the content is probably no longer relevant, but is provided here for posterity.
The active forums are here.
December 07, 2010 6:11pm
Subscribe [7]#16 / Dec 13, 2010 6:04pm
Does that help?
Yes! Thank you Sue!
can you check PHP Info for your max execution time and let us know that that value is?
max_execution_time is 300 local, 300 master.
PHP Version 5.2.11.
Please advise.
#17 / Dec 14, 2010 8:00am
Let me check with the dev team about what values they want you to use. Thanks in advance for your patience.
#18 / Dec 17, 2010 4:00pm
Hi Sue—any news from the developers?
#19 / Dec 17, 2010 4:17pm
Hi, mwdesign -
I believe you’re running into this issue. You might ask your host if they can temporarily increase your max_execution time and try the update again (you’ll need to roll back first). Other possible solutions are in that report.
Let us know how you get on!
#20 / Dec 17, 2010 4:32pm
you’ll need to roll back first
Er—what does that mean? Do I need to reinstall EE v. 1.6.9 again, and start over?
#21 / Dec 17, 2010 5:25pm
You need to roll back to the pre-update process, the original DB.
#22 / Mar 15, 2011 9:12pm
Okay, I rolled back to 1.6.9, increased the max_execution time to 600 seconds, and ran the 2.1.3 installer. Now I get this message:
{"error":"
Error Number: 1050
\n\n
Table 'exp_accessories' already exists
\n\n
CREATE TABLE `exp_accessories` (\n `accessory_id` int(10) unsigned NOT NULL auto_increment,\n `class` varchar(75) NOT NULL default '',\n `member_groups` varchar(50) NOT NULL default 'all',\n `controllers` text NULL,\n `accessory_version` VARCHAR(12) NOT NULL,\n PRIMARY KEY `accessory_id` (`accessory_id`)\n )
\n\n
Filename: updates/ud_200.php
\n\n
Line Number: 1382
"}When I hit the Back button, I get this error:
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: 1382
What am I missing or doing wrong?
#23 / Mar 16, 2011 1:19pm
Hi, mwdesign. When you roll back to your older version, you need to also remove all the 2.x tables that were created during the attempt to upgrade.
What I’d do is drop the database inside of PHPMyAdmin and remake it, then upload your saved .sql file.
Does that make sense?
#24 / Mar 16, 2011 8:40pm
Hi, mwdesign. When you roll back to your older version, you need to also remove all the 2.x tables that were created during the attempt to upgrade. What I’d do is drop the database inside of PHPMyAdmin and remake it, then upload your saved .sql file. Does that make sense?
Hi Sue,
Okay, here’s what I did:
1. Dropped all the tables in the database
2. Uploaded saved .sql file
3. Ran the installer
4. Got this message:
A Database Error Occurred
Error Number: 1050
Table 'exp_accessories' already exists
CREATE TABLE `exp_accessories` ( `accessory_id` int(10) unsigned NOT NULL auto_increment, `class` varchar(75) NOT NULL default '', `member_groups` varchar(50) NOT NULL default 'all', `controllers` text NULL, `accessory_version` VARCHAR(12) NOT NULL, PRIMARY KEY `accessory_id` (`accessory_id`) )
Filename: updates/ud_200.php
Line Number: 1382
« BackSo then I did this:
1. Deleted database
2. Created new database with same name, username, password, etc.
3. Uploaded saved .sql file
4. Ran the installer
5. Got this message:
A Database Error Occurred
Error Number: 1050
Table 'exp_accessories' already exists
CREATE TABLE `exp_accessories` ( `accessory_id` int(10) unsigned NOT NULL auto_increment, `class` varchar(75) NOT NULL default '', `member_groups` varchar(50) NOT NULL default 'all', `controllers` text NULL, `accessory_version` VARCHAR(12) NOT NULL, PRIMARY KEY `accessory_id` (`accessory_id`) )
Filename: updates/ud_200.php
Line Number: 1382
« BackPlease advise. Thanks.
#25 / Mar 17, 2011 2:27pm
OK, if you have emptied out your database container, and you get errors, it means that something got stuck in the upgrade process.
How much memory is allocated to PHP?
Have you seen: EEWiki:// HowTo Determine Memory Limits
-and-
EEWiki:// HowTo Override Memory Limitations
Do you have the ability to use a local install? You may need to do the conversion locally.
How big is the database? Do you have any trackbacks?
#26 / Mar 17, 2011 4:48pm
How much memory is allocated to PHP?
PHP Core Memory Limit: 512M Local/512M Master
How big is the database? Do you have any trackbacks?
Database is 65MB. I have trackbacks. I am not converting them to comments.
Do you have the ability to use a local install? You may need to do the conversion locally.
Where would I find a step-by-step guide for a local install? This is starting to go beyond my capabilities and I’d prefer to avoid this if I can.
#27 / Mar 18, 2011 1:28pm
Hi, mwdesign -
We haven’t actually seen this happen where it’s not an issue with max execution time. Can you confirm what browser you are using for the update?
For a local install, you would need something like MAMP (OSC) or XAMPP (Windows), move your install, as-is, over to local and try the update locally by exporting he files and database, and importing them to your local setup. I’d recommend getting comfortable with this regardless of this issue so that you can have a test bed where you’re not impacting the live site; you may find that valuable for a number of reasons.
#28 / Mar 18, 2011 7:31pm
Can you confirm what browser you are using for the update?
I’ve tried it Firefox 3.6.15, and Safari 5.0.3. Both browsers return the same error.
As a test, I created a new database and I was able to install (not upgrade) the 2.x software without any problems.
For a local install, you would need something like MAMP (OSC) or XAMPP (Windows), move your install, as-is, over to local and try the update locally by exporting he files and database, and importing them to your local setup. I’d recommend getting comfortable with this regardless of this issue so that you can have a test bed where you’re not impacting the live site; you may find that valuable for a number of reasons.
Okay, I’ll give this a try. But before I do, can you please advise which browsers I should use? Thanks.
#29 / Mar 18, 2011 8:01pm
The browser shouldn’t really matter; we’ve seen this in more instances with Firefox and Chrome, which is why I asked, or rather, they gave errors that helped us initially figure out why this happened to some people. But ultimately the browser shouldn’t matter.
Let us know how you do with the development environment!
#30 / Mar 22, 2011 12:16am
If I’m unable to get the database and the update working in MAMP, what options do I have?
One option I’m considering is a clean install of ExpressionEngine 2.x, and re-post all the blog entries. If I were to do this, how could I change the entry date to the date on which the entries were originally posted?
For example, if I was to post an entry today (March 21 2011), how could I change the post so it appears and is entered as January 21 2009?