We launched new forums in March 2019—join us there. In a hurry for help with your website? Get Help Now!
    • 34127
    • 135 Posts
    Well error number 145 means the modx_manager_log table has crashed, and that’s why it can’t be "opened". Did you try repairing it, or running a "check table" in phpMyAdmin?

    If you want to clear everything out, you can use:

    TRUNCATE TABLE `modx_manager_log`


      • 17412
      • 270 Posts
      Hi, I did check the table, phpmyadmin said it was ok. I tried to repair table anyway and then I truncated the table.

      The problem persists :0

      « MODx Parse Error »
      MODx encountered the following error while attempting to parse the requested resource:
      « Execution of a query to the database failed - Can’t open file: ’modx_manager_log.MYI’ (errno: 145) »......
        • 26104
        • 36 Posts
        This still is an issue with the table, not in ModX, in my opinion it could be 2 cases:
        1: Someone changed the permissions on the .MYI file of the table so the MySQL Daemon can not access it anymore.
        2: The table is corrupt, although PHPMyAdmin says it isn’t there still is a possibility that the table is corrupt.

        My solution:
        Try to drop the table and then re-create it.

        If this doesn’t work, backup your database to an SQL file, change the prefix of the tables (from modx_ to something_) with a simple find and replace. Make sure also the manager_log table is created with the new prefix. Now import the new .sql file into PHPMyadmin. When this process is completed change the prefix in manager/includes/config.inc.php and your site will probably work again without errors. Now you can delete the tables with the old prefix. Job’s done.
          • 17412
          • 270 Posts
          Eleventeen - I tried that though for some reason the problem persisted.

          Cheers Sander - I nuked the db as you suggested and it’s back to working again smiley

          Thank you to all of you for your help in this!!