Article ID: 120684, created on Mar 22, 2014, last review on Jul 6, 2016

  • Applies to:
  • Plesk 12.5 for Linux
  • Plesk 11.0 for Linux
  • Plesk 12.5 for Windows
  • Plesk 12.0 for Windows
  • Plesk 11.0 for Windows
  • Plesk 11.5 for Windows


  1. PhpMyAdmin shows the error when I try to insert record into the table.

    #1030 - Got error -1 from storage engine
  2. MySQL does not recognize table:

    mysql> show tables;
    | Tables_in_admin_optest |
    | accounts               |
    1 row in set (0.00 sec)
    mysql> select * from accounts;
    ERROR 1146 (42S02): Table 'admin_optest.accounts' doesn't exist
  3. In Windows logs -> Application, there is error:

        Cannot find or open table admin_optest/accounts from the internal data dictionary of InnoDB though the .frm file for the table exists. Maybe you have deleted and recreated InnoDB data files but have forgotten to delete the corresponding .frm files of InnoDB tables, or you have moved .frm files to another database? or, the table contains indexes that this version of the engine doesn't support.
        See how you can resolve the problem.


  1. The issue happens if you copied MySQL data directory manually which is contains InnoDB databases. InnoDB tables cannot be copied the same way that MyISAM tables can. Just copying the .frm and .ibd files from one location to another is asking for trouble.

  2. Table or database is broken.


  1. Restore Database/table from valid Mysql backup.
  2. Repair databases with System Administrator using Mysql troubleshoot guide:


Search Words

ERROR: PleskFatalException

Table doesn't exist in engine

Installation of WordPress at

msi Error Critical action Configuring MySQL Service has been failed

a914db3fdc7a53ddcfd1b2db8f5a1b9c 56797cefb1efc9130f7c48a7d1db0f0c 46a8e394d6fa13134808921036a34da8 85a92ca67f2200d36506862eaa6ed6b8 bd7fc88cf1b01f097749ae6f87272128 29d1e90fd304f01e6420fbe60f66f838 514af229ae32522202a910a2649c80fb aea4cd7bfd353ad7a1341a257ad4724a 0a53c5a9ca65a74d37ef5c5eaeb55d7f 742559b1631652fadd74764ae8be475e e335d9adf7edffca6a8af8039031a4c7 ed7be2b984f9c27de1d2dc349dc19c6d a766cea0c28e23e978fa78ef81918ab8 8b661cab116c79dbe6c4ac5bbdf1c8cb

Email subscription for changes to this article
Save as PDF