Announcement

Collapse
No announcement yet.

vbulletin database error

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • vbulletin database error

    I'm receiving the following error:

    [error]
    Database error in vBulletin 3.5.3:

    Invalid SQL:

    SELECT threadid, COUNT(*) AS views
    FROM vb3_threadviews
    GROUP BY threadid;

    MySQL Error : Can't open file: 'vb3_threadviews.MYI'. (errno: 145)
    Error Number : 1016
    Date : Tuesday, July 4th 2006 @ 06:11:15 AM
    Script : http://www.wizardsolutionsusa.com/fo...p?&rand=375977
    Referrer : http://www.wizardsolutionsusa.com/fo...p?t=434&page=4
    IP Address : 199.212.18.131
    Username : Unregistered
    [/error]


    It's been going on for a long time now, and I recieve it each time someone visits... (It's sent to my email address)
    Classname : vb_database


  • #2
    This would indicate table corruption. Most specifically, your index file is crashed for the threadviews table. You need to run Repair/Optimize tables in the maintenance section of your AdminCP until all tables report that they are OK. This can take several attempts.
    Translations provided by Google.

    Wayne Luke
    The Rabid Badger - a vBulletin Cloud demonstration site.
    vBulletin 5 API

    Comment


    • #3
      database error

      I am getting a similar error, I can not even access admin cp, each time someone try to visit my site I get an email. I am really new to this, your advise will be really appreciated

      thank you
      Last edited by 52pokercardman; Tue 4 Jul '06, 2:59pm. Reason: grammar

      Comment


      • #4
        You can also repair tables in phpMyAdmin.
        Steve Machol, former vBulletin Customer Support Manager (and NOT retired!)
        Change CKEditor Colors to Match Style (for 4.1.4 and above)

        Steve Machol Photography


        Mankind is the only creature smart enough to know its own history, and dumb enough to ignore it.


        Comment

        widgetinstance 262 (Related Topics) skipped due to lack of content & hide_module_if_empty option.
        Working...
        X