Support » Plugin: iThemes Security (formerly Better WP Security) » Table already exists.

  • Hi Guys,

    We are getting the following error with iThemes Security v7.9.0

    Cannot run iThemes Security. Error encountered during setup. Please try deactivating and reactivating iThemes Security. Contact support if the error persists.

    Table ‘xxxx_itsec_user_groups’ already exists
    Table ‘xxxx_itsec_mutexes’ already exists

    Deactivating and reactivating the plugin does nothing.

    Just wondering what would cause this? And what is your recommendation to resolve it, now and in the future.



Viewing 4 replies - 1 through 4 (of 4 total)
  • Is this during a clean (first time) install or after updating plugin ?

    To prevent any confusion, I’m not iThemes.

    After a quick look at the plugin code I think these errors are specific for updating the plugin from a really old release.

    Is it correct that you are updating from a really old iTSec plugin release ?

    Ignore my previous posts (if not already).

    The iTSec plugin uses the WordPress core dbDelta() function for creating/altering database tables. If a table already exists the create table_name SQL statement is normally ignored by dbDelta().

    Only when a

    describe table_name;

    SQL statement returns nothing (MySQL errors are suppressed), dbDelta() will attempt to create the table.

    So my best guess is that you are probably running into a MySQL privilege issue.

    You could try and log into MySQL (using the same credentials to connect to the database as WordPress is using) and then manually run the SQL statements:

    describe xxxx_itsec_user_groups;
    describe xxxx_itsec_mutexes;

    Where xxxx must be substituted by your database table prefix. If you get an error while these tables do exist you’ll need to resolve that error.

    Thanks nlpro,

    I really appreciate your help and I think you are right about the MYSQL permissions.

    It is for an update to the existing plugin.

    But it is on a custom server setup that has created glitches before. I will point my client’s sysadmins at the MYSQL permissions.

    Thanks again.


Viewing 4 replies - 1 through 4 (of 4 total)
  • You must be logged in to reply to this topic.