I just upgraded my site to 4.7.4 from 4.6.X everything went fairly smoothly after upgrading modules and themes. I have one error I cannot figure out. When I try to enable my upload module I get these errors

* user warning: Table 'airrace_airrace.file_revisions' doesn't exist query: SELECT * FROM files f INNER JOIN file_revisions r ON f.fid = r.fid WHERE r.vid = 2 ORDER BY f.fid in /home/airrace/public_html/includes/database.mysql.inc on line 121.

* user warning: Table 'airrace_airrace.file_revisions' doesn't exist query: SELECT * FROM files f INNER JOIN file_revisions r ON f.fid = r.fid WHERE r.vid = 126 ORDER BY f.fid in /home/airrace/public_html/includes/database.mysql.inc on line 121.

* user warning: Table 'airrace_airrace.file_revisions' doesn't exist query: SELECT * FROM files f INNER JOIN file_revisions r ON f.fid = r.fid WHERE r.vid = 134 ORDER BY f.fid in /home/airrace/public_html/includes/database.mysql.inc on line 121.

I've disabled the File Manager and File Request hoping that it might be related but to no avail. Anyone have any ideas as to what might be causing this? I re-uploaded the upload module in case it had been corrupted when being uploaded the first time, but still get the error. The ability to upload a file with a node is fairly important and it would be great to get it working again. The site is www.airraceclassic.org. Thanks for your help!

Comments

cog.rusty’s picture

Did you run http://yoursite.com/update.php to upgrade Drupal and update the tables to 4.7?

dhw1179’s picture

I ran update.php when I updated the core and eveytime I updated a module.

cog.rusty’s picture

That table should have been created during update. You can see that in /database/update.inc, in system_update_173(). For some reason it did not run.

Take a look in your database to make sure that table does not exist (or perhaps there is a prefix problem or something).

Then you have to find out from which update you need to start. Better in a test installation. All this is not normal...

dhw1179’s picture

Odd. I ran update.php and manually selected system module 173 and the errors disappeared. I guess that fixed it. Thanks! Hopefully no more errors come as a result of this. Worst case I go to my 4.6 back up and redo the update.

cog.rusty’s picture

Now that you ran the updates starting from 173, the only problem case I can think is if you are missing some important updates before 173.