PDA

View Full Version : Error Upgrading from 3.0.3 to 3.6.0


Blue_Chi
Sun 20th Aug '06, 7:27am
I get the following error when I try to access the upgrade script.
Database error in vBulletin :

Invalid SQL:

SELECT *
FROM datastore
WHERE title IN ('','options','bitfields','attachmentcache','forum cache','usergroupcache','stylecache','languagecach e','products','pluginlist','cron','profilefield');

MySQL Error : Table 'o3d.datastore' doesn't exist
Error Number : 1146
Date : Sunday, August 20th 2006 @ 11:19:37 AM
Script : http://www.oman3d.com/forum/install/upgrade.php
Referrer :
IP Address : 85.154.226.249
Username :
Classname : vb_database

Blue_Chi
Sun 20th Aug '06, 9:40am
Okay, I discovered that I had a special table prefix for my vB tables on the database, I edited that I was able to run the upgrade script, however, I faced another problem. When I started the upgrade process, it tells me that I'm updating to version 3.0.4 and then .7 and then .8 and loops between .7 and .8 from there. I tried manually calling the finalupgrade.php script and I got a database error. I restored my database and tried again, but it did not work.

Colin F
Sun 20th Aug '06, 9:43am
It should go from 3.0.4 to 3.0.5 to 3.0.6 and on in that row.
If it's not continuing then you're most likely skipping steps.

Blue_Chi
Sun 20th Aug '06, 9:55am
I am not sure what the problem is, but it just keeps on looping between 6 and 7 now. It gives me the message that says "Your vBulletin version does not appear to match with the version for which this script was created (version 3.0.6).", I am not skipping any steps. I tried restoring my DB a couple of times and this keeps on happening, could it be a caching problem with my browser or something?

Colin F
Sun 20th Aug '06, 9:58am
That's possible. Try using a different browser/computer.

Blue_Chi
Sun 20th Aug '06, 10:32am
Okay, I got it to work, but I had to reload the upgrade.php using a random prefix such as ?random=123 each time I finished each upgrade, I tried different computers and browsers and had the same problem, but that solution made it work.