Announcement

Collapse
No announcement yet.

Upgrade Problem from 3.5.3 > RC3

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Upgrade Problem from 3.5.3 > RC3

    Step 3) Misc Table Alterations
    • Altering setting Table (1 of 2)
    • Altering setting Table (2 of 2)
    • Altering forum Table (1 of 1)
    • Creating externalcache table
    • Altering phrase Table (1 of 7)
    • Altering phrase Table (2 of 7)
    • Altering phrase Table (3 of 7)
    • Altering phrase Table (4 of 7)
    • Altering phrase Table (5 of 7)
    Database error in vBulletin 3.5.4:

    Invalid SQL:
    CREATE INDEX languageid ON phrase (languageid,fieldname);

    MySQL Error : Access denied for user 'web2'@'localhost' to database 'usr_web2_1'
    Error Number : -1


    If i go manually to the next Step i am getting next Error:

    Step 4) Misc Table Alterations
    • Altering subscription Table (1 of 1)
    • Altering user Table (1 of 2)
    • Altering user Table (2 of 2)
    • Altering cron Table (1 of 6)
    • Altering cron Table (2 of 6)
    • Altering cron Table (3 of 6)
    • Altering cron Table (4 of 6)
    • Updating Scheduled Task
    • Updating Scheduled Task
    • Updating Scheduled Task
    • Updating Scheduled Task
    • Updating Scheduled Task
    • Updating Scheduled Task
    • Updating Scheduled Task
    • Updating Scheduled Task
    • Updating Scheduled Task
    • Updating Scheduled Task
    • Updating Scheduled Task
    • Updating Scheduled Task
    • Updating Scheduled Task
    • Altering cron Table (5 of 6)
    • Altering cron Table (6 of 6)
    • Altering cronlog Table (1 of 5)
    • Altering cronlog Table (2 of 5)
    • Altering cronlog Table (3 of 5)
    Database error in vBulletin 3.5.4:

    Invalid SQL:
    CREATE INDEX varname ON cronlog (varname);

    MySQL Error : Access denied for user 'web2'@'localhost' to database 'usr_web2_1'
    Error Number : -1

    thx 4 help

  • #2
    Seems like the MySQL user 'web2'@'localhost' don't have CREATE INDEX permissions to the database 'usr_web2_1'. The MySQL user should have all permissions to the database.

    Is this a test or a production upgrade?

    PS You should never skip to the next step manually if a step failed. Cause of the abort should be fixed, and current upgrade page should be reloaded, or other steps if adviced by Support.
    Want to take your board beyond the standard vBulletin features?
    Visit the official Member to Member support site for vBulletin Modifications: www.vbulletin.org

    Comment


    • #3
      Marco [email protected] now its working on production ...

      Strange, never checked those permissions for the mysql user.

      Comment

      widgetinstance 262 (Related Topics) skipped due to lack of content & hide_module_if_empty option.
      Working...
      X