B2B Marketing Blog - TopRank®

B2B Marketing views, news and interviews.

Contact Us

MENUMENU
  • Services
    • Influencer
      • Start Your B2B Influencer Pilot
    • Content
    • Search
  • Insights
    • Blog
    • News
    • Resources
  • Our Work
    • B2B Technology
    • IT Service Management
    • Project Management Software
    • Social Networks
    • Supply Chain
  • About Us
    • Meet the Team
    • Careers
  • Connect

Fix: WordPress database error: [Can’t open file: ‘wp_comments.MYI’ (errno: 144)]

Lee Odden
Lee Odden
Blogging Strategy

Wordpress ErrorFor the first time this weekend I ran into a rather common WordPress error: WordPress database error: [Can’t open file: ‘wp_comments.MYI’ (errno: 144)]. I also noticed this morning that Matt Cutts is having the same issue. It may seem scary, however, it’s really simple to fix.

To do so, just log into your MySQL database admin area. More than likely that’s done though your webstie’s control panel and phpMyAdmin.

Once in there, locate your blog’s database and bring up the main screen. The main screen is the one that shows you the listing of all the tables. Locate the the wp_comments table in the list and select the checkbox next to it. At the bottom of that page there is a drop down menu that says ‘With selected:’. Chose ‘Repair table’ and repair it. That should do it.

Your comments should come back to life and all should be well again.

[tags]matt-cutts mysql database phpmyadmin[/tags]

About Lee Odden

@LeeOdden is the CEO of TopRank Marketing and editor of TopRank's B2B Marketing Blog. Cited for his expertise by The Economist, Forbes and the Wall Street Journal, he's the author of the book Optimize and presents internationally on B2B marketing topics including content, search, social media and influencer marketing. When not at conferences, consulting, or working with his talented team, he's likely running, traveling or cooking up something new.

Comments

  1. bioephemera says

    January 17, 2007 at 12:49 am

    Thanks! I actually was scared when this happened, and I appreciate your taking the time to post a fix!

  2. Thomas McMahon says

    January 19, 2007 at 10:35 am

    When I first came across it, I freaked too. 🙂

  3. TheBarqsMan says

    January 29, 2007 at 12:25 pm

    Thank you for this simple fix! Worked like a charm from cPanel. I just repaired the entire database and that did the trick.

  4. Thomas McMahon says

    January 30, 2007 at 8:44 am

    No problem. I’m glad to have helped.

  5. chodirin says

    February 11, 2007 at 9:19 am

    thanyou for your solution. its very simple work. just repair our database.

  6. ka edong says

    March 1, 2007 at 5:28 am

    Great help! Thanks!

  7. Adam says

    July 9, 2007 at 6:43 am

    Thanks a million. I didn’t know where to start with this problem but your solution was easy to follow and worked perfectly.

  8. Thomas McMahon says

    July 11, 2007 at 8:09 am

    You’re welcome. I actually don’t think I’ve come across this issue since I upgraded to WordPress 2.2. Not sure if that’s a fix or just luck.

  9. Thorleif Wiik says

    July 24, 2007 at 12:55 pm

    Thank you !!

  10. melvin says

    April 18, 2008 at 2:26 pm

    Thanks a lot, that was really simple.

  11. Dan Hibell says

    April 20, 2008 at 11:53 am

    Thanks for the advice.

    I fixed the error in less than minute!!

    Cheers

  12. Amanda says

    August 18, 2008 at 8:30 pm

    Alrighty, I tried this.. and it took the text off of my blog, but I still cannot leave or see comments. Whats the dealio? And, the text is still there when I go to write a blog.. its just not there on what visitors see. (if that makes sense)

  13. Ted says

    September 29, 2008 at 11:20 am

    A simple solution to fixing an otherwise big loss. Loosing our wordpress comments, would be a nightmare..
    Thanks a lot.

  14. Leslie says

    April 2, 2009 at 1:15 am

    I had this problem today and stumbled upon your fix. Thanks so much!

  15. patrick says

    October 2, 2009 at 8:27 am

    THANK YOU.

    This repaired my blog that's been vomiting errors for months.

  16. Jon says

    December 30, 2009 at 6:35 pm

    Awesome and simple fix! I had an ISPConfig problem with displaying my Server “Monitor” stats and this worked like a dream. Cheers!

Trackbacks

  1. Crappy WordPress Error. at FEWL.NET says:
    February 19, 2007 at 5:53 am

    […] gawdy errors, and I’m behind a firewall that blocks the CPanel port. It’s a pretty easy fix […]

LET’S GET SOCIAL

RSS Feed Twitter Facebook LinkedIn 2022 B2B Influencer Marketing Research Report Elevate B2B Marketing Podcast

Learn about:

SEE TOPRANK MARKETING SPEAK

How to Accelerate B2B Marketing Results by Working With Influencers

SUBSCRIBE        

TOPRANK BLOGGING TEAM

TopRank Marketing Blogging Team

 

Optimize

RECOMMENDED RESOURCES

SEO Blogs

MARKETING BLOG RECOGNITION

CMI

Copyright © 2023 · TopRank Marketing

Return to top of page

We use cookies to understand how you use our site and to improve your experience. This includes personalizing content and advertising. By continuing to use our site, you accept our use of cookies and revised Privacy Policy.