Announcement

Collapse
No announcement yet.

I can't upgrade..

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

  • I can't upgrade..

    Hey,

    I sucessfully moved my vbulletin from 2.2.2 to 2.2.6.

    When I get to the step of upgrading to 2.2.7 (i'm trying to get up to 2.2.9), I get this error:


    Adding new column to session table ... P,BODY{FONT-FAMILY:tahoma,arial,sans-serif;FONT-SIZE:11px;}

    There seems to have been a slight problem with the database.
    Please try again by pressing the refresh button in your browser.
    An E-Mail has been dispatched to our Technical Staff, who you can also contact if the problem persists.
    We apologise for any inconvenience.


    You can check out my forums at www.aznraps.com/forums/. This may also be a factor, as my forums are screwed up in that there is no number 1.-25000 (or some high number, i'm not EXACTLY sure). It starts from around 26000, so the first post is at 26000, and the second post ever was 26001. Let me know if you guys have any idea what's going on.

    Is there any way I can reinstall my forums, while keeping my threads intact? Thanks.

  • #2
    We need to see the entire error message. Either post the contents of the email you received, or right-click on the error page and go to View/Source. Then copy-n-paste the error message here.
    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


    • #3
      Originally posted by Steve Machol
      We need to see the entire error message. Either post the contents of the email you received, or right-click on the error page and go to View/Source. Then copy-n-paste the error message here.
      Here's the error message sent through email:

      Database error in vBulletin :
      Invalid SQL: ALTER TABLE session ADD althash CHAR(32) NOT NULL DEFAULT '' mysql error: Duplicate column name 'althash'
      mysql error number: 1060
      Date: Friday 03rd of January 2003 02:37:55 PM
      Script: /forums/admin/upgrade20.php?step=2
      Referer:
      http://www.aznraps.com/forums/admin/upgrade20.php


      Comment


      • #4
        This error mean that you've already run this script once before. The safest thing to do would be to restore the db backup from just before you started the upgrade process and start all over 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
          Originally posted by Steve Machol
          This error mean that you've already run this script once before. The safest thing to do would be to restore the db backup from just before you started the upgrade process and start all over again.
          is there any way to go about this in a different manner? i ran this script a couple of months ago, and am now just bringing it to attention again to upgrade to the latest version of VB. i don't have any previous backup from that long ago.

          Comment


          • #6
            If you ran it a couple months ago, why are you running it again?

            You should run the upgrade scripts mentioned at http://www.vbulletin.com/members/upgrade.html

            When you last upgraded, from which version to which version did you go to?

            Comment


            • #7
              Originally posted by Cary
              If you ran it a couple months ago, why are you running it again?

              You should run the upgrade scripts mentioned at http://www.vbulletin.com/members/upgrade.html

              When you last upgraded, from which version to which version did you go to?
              i ran it a couple of months ago, and ran into that error. i thought to myself that i would just stick with 2.2.6 until i had more time to get into it. i now have the time to get into the process again, which is why i'm bringing it up.

              i went from one step to the next. i went from 2.2.2, up to 2.2.6. when i was on upgarde20.php, from 2.2.6 to 2.2.7 i ran into that error.

              is there any other possible things to try?

              Comment


              • #8
                Sorry I don't know of any way to do this on a database that has already been partially upgraded. Before you do anything else I suggest you make a current backup of the database. Then try to ignore the error in step 2 and proceed to step 3.
                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


                • #9
                  Originally posted by Steve Machol
                  Sorry I don't know of any way to do this on a database that has already been partially upgraded. Before you do anything else I suggest you make a current backup of the database. Then try to ignore the error in step 2 and proceed to step 3.
                  ha, it worked! thanks!

                  Comment


                  • #10
                    Glad it worked!
                    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

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