Local Install Error

Permalink
I keep getting this message after entering in the mysql database name username and all that:

* mysql error: [1034: Incorrect key file for table 'blocktypes'; try to repair it] in EXECUTE("ALTER TABLE BlockTypes ADD UNIQUE INDEX btHandle (btHandle)")

So I go phpMyAdmin to fix it and when I do, the database populates with 5 or however many tables and then concrete won't let me install because the database isn't empty anymore.

So I go back to phpMyAdmin and delete those tables and I get the same top error and fix it and concrete tells me it needs an empty database and on and on I've gone through this cycle. Can anyone help?

 
bundle replied on at Permalink Reply
bundle
I'm having the same problem. Everything has green check marks in the install requirements and options, yet I keep getting this error:

mysql error: [1034: Incorrect key file for table 'attributekeys'; try to repair it] in EXECUTE("ALTER TABLE AttributeKeys ADD UNIQUE INDEX akHandle (akHandle, akCategoryID)")

This is happening with a fresh local install of version 5.3.3.1. Can anyone help?
paulwoolsey replied on at Permalink Reply 1 Attachment
I'm having an identical error with version 5.4.0.5.

Has anyone found a fix for this?
Mnkras replied on at Permalink Reply
Mnkras
try repairing all tables,

also these posts are almost a year old
joelhansen replied on at Permalink Reply
joelhansen
I have the identical error:
mysql error: [1034: Incorrect key file for table 'blocktypes'; try to repair it] in EXECUTE("ALTER TABLE BlockTypes ADD UNIQUE INDEX btHandle (btHandle);")


I've dropped the db and remade with a new user. The user has the right privileges, and I even tried it with root login.

Mysql databases work with other apps I'm working on.

Thanks for any help!

Concrete 5 - ver. 5.4.1.1
MySQL - ver. 5.1.51
Mnkras replied on at Permalink Reply
Mnkras
The table crashed... run repair on it
joelhansen replied on at Permalink Reply
joelhansen
Haha. Thanks for that advice. I've done that a few times. :P

I think it's MySQL - I was dropping and recreating databases with the same name. Out of frustration I typed in a silly database name and it went through without a hitch.

I wonder if MySQL was remember with same broken database name, even though I was dropping it in between attempts...

Anyway, there we go.