Profile Database Error

[blackenizer]

When I try to look at a profile, I get the following error:

Database error in vBulletin 3.7.0:
Invalid SQL:
SELECT pf.profilefieldcategoryid, pfc.location, pf.*
FROM profilefield AS pf
LEFT JOIN profilefieldcategory AS pfc ON(pfc.profilefieldcategoryid = pf.profilefieldcategoryid)
WHERE pf.form = 0
ORDER BY pfc.displayorder, pf.displayorder;
MySQL Error : Unknown column 'pf.profilefieldcategoryid' in 'field list'
Error Number : 1054
Request Date : Friday, May 2nd 2008 @ 06:18:37 PM
Error Date : Friday, May 2nd 2008 @ 06:18:38 PM
Script : http://www.blackenize.com/forums/member.php?u=3811
Referrer : http://www.blackenize.com/forums/index.php
IP Address : 167.193.134.61
Username : Blackenizer
Classname : vB_Database
MySQL Version : 4.1.22-standard-log

[Steve Machol]

That appears to be from an add-on or old code.

To troubleshoot this, first reupload all the original vB non-image files (except install.php). Make sure you upload these in ASCII format and overwrite the ones on the server. Also be sure to upload the admincp files to whichever directory you have set in your config.php file. Then run 'Suspect File Versions' in Diagnostics to make sure you have all the original files for your version and that none show 'File does not contain expected contents':

Admin CP -> Maintenance -> Diagnostics -> Suspect File Versions

[Note: In some cases you may also need to remove any of the listed .xml files in the includes/xml directory.]

Next, disable all plugins.

Note: To temporarily disable the plugin system, edit config.php and add this line right under <?php

define('DISABLE_HOOKS', true);

Then if you still have this problem, create a new style and choose no parent style. This will force it to use the default templates. Finally empty your browser cache, close all browser windows then try again. Make sure you change to the new style and view your forums with it. Do you have the same problem?

[blackenizer]

Tried that several times and still get same error.

[blackenizer]

Okay, I did an upgrade to 3.6.4 to 3.6.7 and then to 3.7.0. It fixed the problem.