PDA

View Full Version : Upgrade error: to 3.7 step 4



Thomas P
Sun 12th Oct '08, 2:42pm
Hello,

we are currently testing an upgrade in our testbed and get the following error:

http:// foo /install/upgrade_370b2.php?step=4

Step 4) Default Data Insertion

* Updating phrasetype table
* Altering usergroup Table (1 of 1)

Database Error Database error
The foo Forum database has encountered a problem.
Please try the following:

* Load the page again by clicking the Refresh button in your web browser.
* Open the foo home page, then try to open another page.
* Click the Back button to try another link.

The foo forum technical staff have been notified of the error, though you may contact them if the problem persists.

We apologise for any inconvenience.

Here is the error:
Database error in vBulletin:

Invalid SQL:
UPDATE usergroup SET
forumpermissions = forumpermissions |
IF(forumpermissions & 16, 1048576, 0) |
IF(forumpermissions & 64, 2097152, 0) |
IF(forumpermissions & 512, 4194304, 0),
genericpermissions = genericpermissions |
IF(forumpermissions & 64
OR forumpermissions & 16, 1073741824, 0),

genericpermissions2 = genericpermissions2 |
IF(genericpermissions & 4096
OR genericpermissions & 268435456, 1, 0),

albumpermissions = albumpermissions |
IF(genericpermissions & 2
AND genericpermissions & 128, 1, 0) |
IF(genericpermissions & 1, 2, 0),
albumpicmaxwidth = 600,
albumpicmaxheight = 600,
albumpicmaxsize = 100000,
albummaxpics = 100,
albummaxsize = 0,

usercsspermissions = usercsspermissions |
IF(genericpermissions & 2
AND signaturepermissions & 8, 1, 0) |
IF(genericpermissions & 2
AND signaturepermissions & 8, 2, 0) |
IF(genericpermissions & 2
AND signaturepermissions & 2, 4, 0) |
IF(genericpermissions & 2
AND genericpermissions & 128
AND signaturepermissions & 2, 8, 0) |
IF(genericpermissions & 2
AND signaturepermissions & 2, 16, 0),

visitormessagepermissions = visitormessagepermissions |
IF(forumpermissions & 64
OR forumpermissions & 32, 1, 0) |
IF(forumpermissions & 64, 2, 0) |
IF(forumpermissions & 128, 4, 0) |
IF(forumpermissions & 256, 8, 0) |
IF(forumpermissions & 131072, 16, 0) |
IF(forumpermissions & 128
OR forumpermissions & 256, 32, 0),

socialgrouppermissions = socialgrouppermissions |
IF(genericpermissions & 1, 1, 0) |
IF(forumpermissions & 16, 2, 0) |
IF(forumpermissions & 128, 4, 0) |
IF(forumpermissions & 512, 8, 0) |
IF(genericpermissions & 1, 16, 0) |
IF(forumpermissions & 128
OR forumpermissions & 256, 32, 0) |
IF(adminpermissions & 1, , 0) |
64;

MySQL Error : You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near ' 0) |
64' at line 55
Error Number : 1064
Request Date : Sunday, October 12th 2008 @ 07:34:08 PM
Error Date : Sunday, October 12th 2008 @ 07:34:08 PM
Script : http:// foo /install/upgrade_370b2.php?step=4
Referrer : http:// foo /install/upgrade_370b2.php?step=3
IP Address :
Username :
Classname : vB_Database
MySQL Version : 5.0.51b-log

When looking at the database I see that most of the tables are in 'latin1_swedish_ci', the new ones which are created by the script are in 'utf8_general_ci' - is this the reason?

Thanks,
Tom

Thomas P
Sun 12th Oct '08, 4:58pm
Strange, converting to 3.7 and later to 3.8 works (?)

Thomas P
Mon 20th Oct '08, 8:48am
Is this fixed...? Or is it only me who get's that error?


UPDATE usergroup SET
(...)
OR forumpermissions & 256, 32, 0),

socialgrouppermissions = socialgrouppermissions |
IF(genericpermissions & 1, 1, 0) |
IF(forumpermissions & 16, 2, 0) |
IF(forumpermissions & 128, 4, 0) |
IF(forumpermissions & 512, 8, 0) |
IF(genericpermissions & 1, 16, 0) |
IF(forumpermissions & 128
OR forumpermissions & 256, 32, 0) |
IF(adminpermissions & 1, , 0) |
64;

MySQL Error : You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near ' 0) |
64' at line 55

Zachery
Mon 20th Oct '08, 8:53am
I'd suggest reporting a bug.

Morrus
Mon 20th Oct '08, 8:08pm
I had the exact same thing, Thomas P. I'm trying the same thing you did.

alexi
Mon 3rd Nov '08, 2:06am
Me too- the fix mentioned above, upgrading to 3.7 first also worked for me

MGSteve
Mon 10th Nov '08, 11:10am
I've just got this upgrading to 3.80b2, but oddly I didn't get it when I upgraded to 3.73 last week on the same server (it was a dry run).

I'll use the 3.73 files and upgrade to that and then upgrade to 3.80b2 from that.