[Forum] Database error after upgrade: albumpicture does not exist

[Mandi]

It seems my upgrade process did not create an expected table (in fact, it's not there - it's not listed under repair/optimize tables).

Upon completing my upgrade, I did have five templates that had to be reverted. I did so, and ran the upgrade script again . . . the database error persists. (I didn't think reverting the templates would fix it, but I had hoped re-running upgrade might!)

Strangely, I am getting the expected "Sorry, our forum is turned off for a bit . . . " custom message in Firefox, but the database error page in IE. Weird. (I have friendly error messages turned off in my IE settings, too.)

Here is the output from the database error message:

Database error in vBulletin 4.0.0:

Invalid SQL:

  SELECT albumpicture.*, album.*, user.username, user.usergroupid,
  IF(displaygroupid=0, user.usergroupid, displaygroupid) AS displaygroupid 
  FROM albumpicture AS albumpicture
  LEFT JOIN album AS album ON(album.albumid = albumpicture.albumid)
  LEFT JOIN user AS user ON(user.userid = album.userid)
  WHERE album.state = 'public' 
  ORDER BY dateline DESC LIMIT 0, 5;

MySQL Error   : Table 'xyaaps-forum.albumpicture' doesn't exist
Error Number  : 1146
Request Date  : Friday, December 25th 2009 @ 08:00:51 AM
Error Date    : Friday, December 25th 2009 @ 08:00:51 AM
Script        : http://www.yaaps.com/forums/index.php
Referrer      : http://www.yaaps.com/forums/admincp/index.php?do=head
IP Address    : 76.24.127.117
Username      : YAAPS
Classname     : vB_Database
MySQL Version : 5.0.84-log

What should I try next? Thanks for any help you can offer!

[Mandi]

I noticed I had not run the thread updates (etc.) and so did this just now . . . still throwing the same database error. (Not that I am surprised, just to be thorough about the install and all.)

[Dody]

Looks like you are using a plugin. Disable all your plugins and try again.

[Mandi]

That was it, thanks! I failed to recognize the table as being a plugin, not a native vB item.

[turbosatan]

thanks this helped me. as a quick note. i got this when using vbadvanced as homepage and i had old modules installed which wewre trying to access 3.8 tables when i was using 4.2