No announcement yet.

Error in database

  • Filter
  • Time
  • Show
Clear All
new posts

  • Error in database

    I receive on my admin account some errors from users. Is the same error:

    Database error in vBulletin 3.6.0 Beta 4:

    Invalid SQL:

    SELECT post.postid, post.title, post.pagetext, post.dateline, post.userid, post.visible AS postvisible,
    IF(user.username, user.username, post.username) AS username,
    thread.threadid, thread.title AS threadtitle, thread.postuserid, thread.visible AS threadvisible,
    forum.forumid, forum.password
    FROM post AS post
    LEFT JOIN user AS user ON (post.userid = user.userid)
    INNER JOIN thread AS thread ON (post.threadid = thread.threadid)
    INNER JOIN forum AS forum ON (thread.forumid = forum.forumid)
    WHERE post.postid IN ();

    MySQL Error : Aveti o eroare in sintaxa RSQL linga ')' pe linia 9
    Error Number : 1064
    Date : Friday, July 7th 2006 @ 06:27:44 PM
    Script :
    Referrer :
    IP Address :
    Username : ZEROSASE
    Classname : vB_Database

  • #2
    Did you customize your files?
    Change the MySQL database table(s) field(s)?
    Do you run any plugins?


    • #3
      I use no custonization.

      The error shows when pressing "go advanced" from fast reply.

      I created a new style and the error is the same.


      • #4
        Is there a way to solve this? The support ticket is not in user anymore?


        • #5
          First I recommend reuploading all the default vBulletin non-image files in ASCII mode, overwriting your current files. Also, turn off plugins globally in your vBulletin Options. Does this problem still occur then?
          Best Regards
          Colin Frei

          Please don't contact me per PM.


          • #6
            I reuploaded all non-image files in Ascii, after that I disabled the plugins.

            The same error occurs...


            • #7
              I upgraded to 3.6 RC 1. Now I get no error when pressing "Go advanced" button. I get an error when trying to view member list:

              Database error in vBulletin 3.6.0 Release Candidate 1:

              Invalid SQL:

              SELECT user.*,usertextfield.*,userfield.*, user.userid, options,
              IF(displaygroupid=0, user.usergroupid, displaygroupid) AS displaygroupid

              ,avatar.avatarpath,NOT ISNULL(customavatar.userid) AS hascustomavatar,customavatar.dateline AS avatardateline, customavatar.width AS avwidth, customavatar.height AS avheight

              , lastactivity AS lastvisittime

              FROM user AS user
              LEFT JOIN usertextfield AS usertextfield ON(usertextfield.userid=user.userid)
              LEFT JOIN userfield AS userfield ON(userfield.userid=user.userid)

              LEFT JOIN avatar AS avatar ON(avatar.avatarid = user.avatarid) LEFT JOIN customavatar AS customavatar ON(customavatar.userid = user.userid)

              WHERE 1=1
              AND user.usergroupid IN (-1,6,8,20,7,2,22,5)
              ORDER BY user.username asc
              LIMIT 0, 30;

              MySQL Error : Eroarea 134 obtinuta din handlerul tabelei
              Error Number : 1030
              Date : Thursday, July 13th 2006 @ 12:06:31 AM
              Script :
              Referrer :
              IP Address :
              Username : Vadim
              Classname : vB_Database


              • #8
                MySQL error: 134 = Record was already deleted (or record file crashed)

                To fix this run Repair/Optimize in the Admin CP. You may need to run it more than once to fix all

                Admin CP -> Maintenance -> Repair/Optimize Tables -> Check All -> Continue

                If you cannot access the Admin CP you can also use phpMyAdmin to repair tables.
                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.


                • #9
                  All is ok, I think the forum made his automatic scheduled task and the next day all was ok... It was not necessary anymore to run "repair tables".


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