It is probably coming from SP.
You can go to the Forum admin > Tool Box > Error log and look for something that says there is a database error.

Copy and paste the latest one here and someone can help from there.

Also if you updated Simple:Press to the latest version but see some SP Plugins that need to be updated then update them and see if the issue is resolved.

All my plugins are updated and I’m using the latest version of SP.

Thanks

I think the ‘Incorrect key file for table’ error normally comes down to a space issue, and they both reference cache so it could be that temporary files are taking up a lot of room.

Do you maintain the database? i.e cleanup?

Also, have you tried a repair at all as suggested in the first error?

I agree that the repair is most probably the important bit of info in there. Looks likely that you have a corruopt table.

Do you have a regime of table and database optimisation in place? If not then I would do so as yours, I believe, is quite a busy site and would benefit from at least weekly optimisation. It will also help tables from becoming fragmented and eventually corrupted which is probably the case here.

If your host can not help then I would use a plugin like – WP db Manager – I believe it is called – that will carry our repairs and checks on demand but also allow you to schedule regular optimisations.

Done and it worked. Thanks guys. Best support ever.

Great news. Worth noting that an un-optimised database that starts to fragment can also be a drag in performance as it has to work harder to compile query results. Just another good reason for regular optimisation.

question about this yellow, how do the innodb tables fall into this? every time I optimize my database through phpadmin, it says those tables can not be optimized, which is all the sp tables

Do you know I have never investigated that and will clearly have to. InnoDB tables are more efficient and lock by row instead of table during operations. It might be that they do not fragment in quite the same way.

I will google it….

I ggogled it last night after reading this thread and came across this on stack overflow

For InnoDB tables, OPTIMIZE TABLE is mapped to ALTER TABLE, which rebuilds the table to update index statistics and free unused space in the clustered index. Beginning with MySQL 5.1.27, this is displayed in the output of OPTIMIZE TABLE when you run it on an InnoDB table, as shown here:

You can make OPTIMIZE TABLE work on other storage engines by starting mysqld with the –skip-new or –safe-mode option. In this case, OPTIMIZE TABLE is just mapped to ALTER TABLE.

http://stackoverflow.com/questions/2816044/optimize-innodb-table

but I have no clue what that means lol

I have to say that Stack Overflow always seems to me to be either spot on or a long way off! I don’t see evidence to back this up on the MySQL documentation website pages I have looked at so far. I have also just tried an optimise run against my own innoDB based database tables with no problems whatsoever. 

The one thing it did suggest however is that you really only need to optimise when the database starts to get big although defining big is the same as the length of a piece of string. To quote:

Once your data reaches a stable size, or a growing table has increased by tens or some hundreds of megabytes, consider using the OPTIMIZE TABLE statement to reorganize the table and compact any wasted space. The reorganized tables require less disk I/O to perform full table scans.

so – if you are getting an error back from an optimise attempt I think i would be asking your host why that is to be honest – as it appears there should be no issue doing so.

I will pose the question, what version of sql are you using? we have 5.5.4

I am using version 5.5.29…