Announcement

Collapse
No announcement yet.

Problems with vB2 to vB3 upgrade

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

  • Problems with vB2 to vB3 upgrade

    I'm trying to upgrade my vBulletin 2.3.0 to 3.0.1, and I am running into a couple problems. First, after uploading my vB3 files onto the server and running upgrade.php, I receive the following error:
    Code:
    Database error in vBulletin 3.0.0 Beta 3:
     
     Invalid SQL: 
     		SELECT *
     		FROM session
     		WHERE sessionhash = '5d9e405fc8b7a5ea08350cce3ac167a0'
     		AND lastactivity > 1084172580
     		AND host = '68.231.96.174'
     		AND idhash = 'e08651be5a810e4a4fbc99df50b30f9c'
     	
     mysql error: Unknown column 'idhash' in 'where clause'
     
     mysql error number: 1054
     
     Date: Monday 10th of May 2004 12:19:40 AM
     Script: XXXXXXXXXX
     Referer: 
     IP Address: XXXXXXXXX
    The main thing in the above error that catches my (untrained) eye is that it mentions "vBulletin 3.0.0 Beta 3" but I'm 100% positive that I've downloaded vB 3.0.1.

    Also, I have ran the database conflicts script and come up with all kinds of listings:
    Table Conflicts</p>
    • Table Conflict for adminhelp
    • Table Conflict for administrator
    • Table Conflict for attachmenttype
    • Table Conflict for attachmentviews
    • Table Conflict for calendar
    • Table Conflict for calendarcustomfield
    • Table Conflict for calendarmoderator
    • Table Conflict for calendarpermission
    • Table Conflict for cron
    • Table Conflict for cronlog
    • Table Conflict for customprofilepic
    • Table Conflict for datastore
    • Table Conflict for deletionlog
    • Table Conflict for editlog
    • Table Conflict for faq
    • Table Conflict for holiday
    • Table Conflict for imagecategory
    • Table Conflict for imagecategorypermission
    • Table Conflict for language
    • Table Conflict for mailqueue
    • Table Conflict for moderation
    • Table Conflict for moderatorlog
    • Table Conflict for passwordhistory
    • Table Conflict for phrase
    • Table Conflict for phrasetype
    • Table Conflict for pm
    • Table Conflict for pmreceipt
    • Table Conflict for pmtext
    • Table Conflict for post_parsed
    • Table Conflict for posthash
    • Table Conflict for ranks
    • Table Conflict for reminder
    • Table Conflict for reputation
    • Table Conflict for reputationlevel
    • Table Conflict for stats
    • Table Conflict for strikes
    • Table Conflict for subscribeevent
    • Table Conflict for subscription
    • Table Conflict for subscriptionlog
    • Table Conflict for threadviews
    • Table Conflict for userban
    • Table Conflict for usergroupleader
    • Table Conflict for usergrouprequest
    • Table Conflict for usernote
    • Table Conflict for userpromotion
    • Table Conflict for usertextfield
    Column Conflictstemplate
    • Column Conflict for version

    I'm absolutely lost! I'd really love to be able to upgrade, so any help would be appreciated!

    P.S. I do not have Telnet/SSH access to this server, only Webmin & FTP access.
    Last edited by JaZz0r; Mon 10 May '04, 1:38am.

  • #2
    You can only run table_conficlits script on a vB2 databases, once the upgrade process has begun you cannot run the script.

    Its saying beta 3 because you need to update though all the betas > gamma > RC > Gold.

    Had you installed any hacks before the upgrade?

    Comment


    • #3
      AFAIK, the database has always been vB2. I had attempted to upgrade to an earlier 3.0 beta, but ended up rolling back to my backup database (which should not have had any 3.0 entries). My current upgrade attempt has not even allowed me to see the first page of the process.

      In the 3+ years this database has been active, there have been hacks added and removed here and there.

      Comment


      • #4
        The extra tables are from the failed upgrade. You need to restore a clean vB2 backup to a new database and try again.
        Steve Machol, former vBulletin Customer Support Manager (and NOT retired!)
        Change CKEditor Colors to Match Style (for 4.1.4 and above)

        Steve Machol Photography


        Mankind is the only creature smart enough to know its own history, and dumb enough to ignore it.


        Comment


        • #5
          Hi Steve. Glad to see a fellow Arizonian -- hopefully your workplace is a lot less warm than mine!

          If the failed upgrade you are referring to has anything to do with the 3.0 beta upgrade I attempted, this is going to be a problem. I am very sure I had rolled back to my clean vB2 database after running into problems with that beta and I am very confused as to why this is happening. This was quite a while ago and I don't fully recall the details of that situation.

          Would it be possible to use the vB2 control panel and backup only the pertinent tables that the vB3 upgrade would require? I believe that would be my only option...

          Comment


          • #6
            The problem is that when you restored the vB2 database, it left in place the vB3 tables created from the failed backup - at least the ones that don't have the same names as tables in vB2. Unless ou can restore this to a new databaser, your only other option is to manually drop all the Table Conflict tables. You'll also have to drop the version column in the template table.
            Steve Machol, former vBulletin Customer Support Manager (and NOT retired!)
            Change CKEditor Colors to Match Style (for 4.1.4 and above)

            Steve Machol Photography


            Mankind is the only creature smart enough to know its own history, and dumb enough to ignore it.


            Comment


            • #7
              I will be putting vB3 into a new database separate from the current vB2 database. To confirm, I can safely remove all the tables mentioned in the database conflict script from the new database to perform the upgrade?

              Comment


              • #8
                Do backup before you start to do anything.

                Comment


                • #9
                  Of course! I will not be messing around with the live database until I am able to successfully upgrade a copy of it.

                  Comment

                  Loading...
                  Working...
                  X