Title: errors when attempting to activate the plugin
Last modified: January 30, 2023

---

# errors when attempting to activate the plugin

 *  Resolved [sikitraki](https://wordpress.org/support/users/sikitraki/)
 * (@sikitraki)
 * [3 years, 4 months ago](https://wordpress.org/support/topic/errors-when-attempting-to-activate-the-plugin/)
 * Hi Support Team
   I have installed the ithemes security plugin in my site and upon
   activation we receive the following error(s):
 * Cannot run iThemes Security. Error encountered during setup. Please try deactivating
   and reactivating iThemes Security. Contact support if the error persists.
    1.  [Microsoft][ODBC Driver 17 for SQL Server][SQL Server]There is already an object
        named ‘wp_itsec_logs’ in the database. Code – 2714
    2.  [Microsoft][ODBC Driver 17 for SQL Server][SQL Server]The definition for column‘
        lockout_conNVARCHAR’ must include a data type. Code – 173
    3.  [Microsoft][ODBC Driver 17 for SQL Server][SQL Server]There is already an object
        named ‘wp_itsec_temp’ in the database. Code – 2714
    4.  [Microsoft][ODBC Driver 17 for SQL Server][SQL Server]There is already an object
        named ‘wp_itsec_distributed_storage’ in the database. Code – 2714
    5.  [Microsoft][ODBC Driver 17 for SQL Server][SQL Server]There is already an object
        named ‘wp_itsec_geolocation_cache’ in the database. Code – 2714
    6.  [Microsoft][ODBC Driver 17 for SQL Server][SQL Server]There is already an object
        named ‘wp_itsec_fingerprints’ in the database. Code – 2714
    7.  [Microsoft][ODBC Driver 17 for SQL Server][SQL Server]There is already an object
        named ‘wp_itsec_opaque_tokens’ in the database. Code – 2714
    8.  [Microsoft][ODBC Driver 17 for SQL Server][SQL Server]There is already an object
        named ‘wp_itsec_user_groups’ in the database. Code – 2714
    9.  [Microsoft][ODBC Driver 17 for SQL Server][SQL Server]There is already an object
        named ‘wp_itsec_mutexes’ in the database. Code – 2714
    10. [Microsoft][ODBC Driver 17 for SQL Server][SQL Server]There is already an object
        named ‘wp_itsec_bans’ in the database. Code – 2714
    11. [Microsoft][ODBC Driver 17 for SQL Server][SQL Server]There is already an object
        named ‘wp_itsec_dashboard_events’ in the database. Code – 2714
    12. The itsec_lockouts table is not installed.
 * A plugin deactivation/reactivation nor a complete plugin reinstall solved the
   problem. One important note is that we use ProjectNami WordPress. Are there any
   post-activation setup steps needed when using ProjectNami?
   Please adviseThanks!

Viewing 5 replies - 1 through 5 (of 5 total)

 *  Plugin Support [chandelierrr](https://wordpress.org/support/users/shanedelierrr/)
 * (@shanedelierrr)
 * [3 years, 4 months ago](https://wordpress.org/support/topic/errors-when-attempting-to-activate-the-plugin/#post-16424126)
 * Hi [@sikitraki](https://wordpress.org/support/users/sikitraki/), thanks for reaching
   out. Unfortunately, iTSec doesn’t support SQL Server, which is why it cannot 
   run on your site.
 *  [nlpro](https://wordpress.org/support/users/nlpro/)
 * (@nlpro)
 * [3 years, 4 months ago](https://wordpress.org/support/topic/errors-when-attempting-to-activate-the-plugin/#post-16424288)
 * Hi [@sikitraki](https://wordpress.org/support/users/sikitraki/),
 * It does look like the plugin gets activated (despite the errors) or not?
 * It seems to me the `Code – 2714` errors are non fatal and can simply be ignored.
   However there is one other error, `Code – 173`, which prevents the **wp_itsec_lockouts**
   table from being created (“The itsec_lockouts table is not installed”). And that
   is a real problem, since the iTSec plugin needs that table.
 * It looks like the MySQL create table statement for the **wp_itsec_lockouts** 
   table is not properly converted into a MS SQL Server equivalent, which sounds
   like a bug in ProjectNami. It seems to stumble on the lockout_context column 
   which looks like this in MySQL:
 * `lockout_context TEXT`
 * And ProjectNami attempts to (stupidly) convert that into:
 * `lockout_conNVARCHAR`
 * While it should be:
 * `lockout_context NVARCHAR`
 * Suppose this 1 issue gets fixed (or as a workaround you can manually create the**
   wp_itsec_lockouts** table in the MS SQL Server database) it would be interesting
   to see whether the iTSec plugin actually works in ProjectNami. No guarantees 
   though 😉
 * +++++ To prevent any confusion, I’m not iThemes +++++
 *  Plugin Support [chandelierrr](https://wordpress.org/support/users/shanedelierrr/)
 * (@shanedelierrr)
 * [3 years, 4 months ago](https://wordpress.org/support/topic/errors-when-attempting-to-activate-the-plugin/#post-16424339)
 * [@nlpro](https://wordpress.org/support/users/nlpro/) [this](https://github.com/ProjectNami/projectnami/issues/414)
   might be related, but I’m not sure if the fix applied addresses the `Code – 173`
 *  [nlpro](https://wordpress.org/support/users/nlpro/)
 * (@nlpro)
 * [3 years, 4 months ago](https://wordpress.org/support/topic/errors-when-attempting-to-activate-the-plugin/#post-16424433)
 * Hi [@shanedelierrr](https://wordpress.org/support/users/shanedelierrr/),
 * It’s also a conversion issue, but a little bit different.
 * > …but I’m not sure if the fix applied addresses the `Code – 173`
 * No, it doesn’t.
 * [This](https://github.com/ProjectNami/projectnami/issues/346) looks like an identical(
   and still open/unfixed) issue. Opened in April 2019…
    -  This reply was modified 3 years, 4 months ago by [nlpro](https://wordpress.org/support/users/nlpro/).
 *  [nlpro](https://wordpress.org/support/users/nlpro/)
 * (@nlpro)
 * [3 years, 4 months ago](https://wordpress.org/support/topic/errors-when-attempting-to-activate-the-plugin/#post-16425798)
 * Hi [@sikitraki](https://wordpress.org/support/users/sikitraki/),
 * In order to get the **wp_itsec_lockouts** table created on plugin activation 
   try and add the code below to the active theme functions.php file:
 *     ```wp-block-code
       add_filter( 'pre_translate_query', 'itsec_ptq' );
   
       function itsec_ptq( $query ) {
       	$query = str_replace( 'lockout_context TEXT,', 'lockout_coNTEXT TEXT,', $query );
       	return $query;
       }
       ```
   
 * Note this is a ProjectNami specific filter. It does not exist in regular WordPress
   core. So it is undocumented in the Code Reference on developer.wordpress.org
 * Also the code snippet above is untested. I expect it to work but it may need 
   some further tweaking. Try it and let us know the result.
    -  This reply was modified 3 years, 4 months ago by [nlpro](https://wordpress.org/support/users/nlpro/).

Viewing 5 replies - 1 through 5 (of 5 total)

The topic ‘errors when attempting to activate the plugin’ is closed to new replies.

 * ![](https://ps.w.org/better-wp-security/assets/icon.svg?rev=3529351)
 * [Kadence Security – Password, Two Factor Authentication, and Brute Force Protection](https://wordpress.org/plugins/better-wp-security/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/better-wp-security/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/better-wp-security/)
 * [Active Topics](https://wordpress.org/support/plugin/better-wp-security/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/better-wp-security/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/better-wp-security/reviews/)

 * 5 replies
 * 3 participants
 * Last reply from: [nlpro](https://wordpress.org/support/users/nlpro/)
 * Last activity: [3 years, 4 months ago](https://wordpress.org/support/topic/errors-when-attempting-to-activate-the-plugin/#post-16425798)
 * Status: resolved