Announcement

Collapse
No announcement yet.

Problem upgrading to 5.1.0

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

  • Problem upgrading to 5.1.0

    I have received an abort error when attempting to upgrade from 5.0.5 to 5.1.0. Here is the progress and where it fails, at 98% complete:
    • Upgrading to 5.0.5
    • Upgrading to 5.0.6 Alpha 1
    • Step 1 - Altering setting Table (1 of 2)
    • Altering settinggroup Table (1 of 2)
    • Updating administrative permissions
    • Step 2 - Skipping step, not needed
    • Upgrading to 5.0.6
    • Upgrading to 5.1.0 Alpha 1
    • Step 1 - Updating site table
    • The next step may take a long time, please be patient.
    • Step 2 - Removing CMS DATA from Special channel before re-importing. The next few steps may take a while, please be patient.
    • Step 3 - Updating widget table
    • Step 4 - Updating pagetemplate table
    • Step 5 - Updating page table
    • Step 6 - Updating channel table
    • Step 7 - Updating routenew table
    • Step 8 - Importing CMS Home Page Information
    • Step 9 - Processed 5 records
    • Step 9 - Processed 1 records
    • Step 9 - Process done
    • Processed records 1 - 50 (of 112)
    • Processed records 51 - 100 (of 112)
    • Processed records 101 - 112 (of 112)
    • Step 10 - Process done
    • Processed records 21780 - 21780 (of 21780)
    • Step 11 - Process done
    • Step 12 - Setting CMS permissions
    • Processed records 1 - 53 (of 53)
    • Step 13 - Process done
    • Processed records 24679 - 24699 (of 24699)
    • Step 14 - Process done
    • Step 15 - Skipping step, not needed
    • Step 16 - Process done
    • Step 17 - Skipping step, not needed
    • Step 18 - Skipping step, not needed
    • Step 19 - Updating adminmessage table
    • Upgrading to 5.1.0 Alpha 2
    • Step 1 - Granting CMS Admin permissions to users who had vB4 CMS Admin Permissions, if any
    • The next step may take a long time, please be patient.
    • Step 2 - Altering node Table (1 of 2)
    • The next step may take a long time, please be patient.
    • Step 3 - Setting public_preview field for imported nodes with public preview set.
    • Step 4 - Altering node Table (2 of 2)
    • Step 5 - Altering cron Table (1 of 1)
    • Importing CMS tags from vBulletin 4 CMS.
    • Processing 1000 records
    • Step 6 - Importing CMS tags from vBulletin 4 CMS.
    • Process done
    • Step 7 - Importing CMS Categories as Tags.
    • Importing CMS tags from vBulletin 4 CMS.
    • Processing 1000 records
    • Step 8 - Importing CMS tags from vBulletin 4 CMS.
    • Process done
    • Step 9 - Setting nodeoptions for imported CMS nodes.
    • Setting node taglist field for imported CMS nodes.
    • Processing 500 records
    • Step 10 - Setting node taglist field for imported CMS nodes.
    • Process done
    • Step 11 - Updating legacy redirect route for CMS nodes.
    • Upgrading to 5.1.0 Alpha 3
    • Upgrading to 5.1.0 Alpha 4
    • Step 1 - Updating displayorder for blog channels.
    • Process done
    • Step 2 - Updating displayorder for social group channels.
    • Processed records 24286 - 24286
    • Step 2 - Process done
    • Step 3 - Updating link preview images.
    • Process done
    • Upgrading to 5.1.0 Alpha 5
    • Step 1 - The next step may take a long time, please be patient.
    • Updating article preview images.
    • Processed records 24679 - 24699
    • Step 2 - Process done
    • Step 3 - Updating permission table
    • Step 4 - Updating permission table
    • Upgrading to 5.1.0 Alpha 6
    • Step 1 - Updating CMS article channel options.
    • Upgrading to 5.1.0 Alpha 7
    • Step 1 - Removing duplicate page record.
    • Upgrading to 5.1.0 Alpha 8
    • Step 1 - The next step may take a long time, please be patient.
    • Step 2 - Altering node Table (1 of 1)
    • Fixing imported polls.
    • Step 3 - Fixing imported polls.
    • Process done
    • Upgrading to 5.1.0 Alpha 9
    • Step 1 - Altering passwordhistory Table (1 of 4)
    • Altering passwordhistory Table (2 of 4)
    • Altering passwordhistory Table (3 of 4)
    • Step 2 - Altering passwordhistory Table (4 of 4)
    • Step 3 - Altering user Table (1 of 5)
    • Step 4 - Altering user Table (2 of 5)
    • Step 5 - Altering user Table (3 of 5)
    • Step 6 - Updating password schemes.
    • Step 7 - Updating password tokens.
    • Step 8 - Altering user Table (4 of 5)
    • Upgrading to 5.1.0 Beta 1
    • Upgrading to 5.1.0 Beta 2
    • Step 1 - Updating channel permissions for channel moderators
    • Step 2 - Skipping step, not needed
    • Upgrading to 5.1.0 Beta 3
    • Upgrading to 5.1.0 Beta 4
    • Upgrading to 5.1.0 Release Candidate 1
    • Upgrading to 5.1.0
    • Processing XML
    • Step 1 - Import latest options
    • Importing vbulletin-settings.xml
    • Import Done
    • Step 2 - Import latest admin help
    • Importing vbulletin-adminhelp.xml
    • Import Done
    • Step 3 - Import latest language
    • Importing vbulletin-language.xml
    • Import Done
    • Step 4 - Import latest widgets
    • Importing vbulletin-widgets.xml
    • Import Done
    • Step 5 - Importing vbulletin-pagetemplates.xml
    • Import Done
    • Step 6 - Importing vbulletin-pages.xml
    • Import Done
    • Step 7 - Importing vbulletin-channels.xml
    • Import Done
    • Step 8 - Importing vbulletin-routes.xml
    • Import Done
    • Step 9 - Skipping step, not needed
    • Step 10 - Creating new routes
    • Step 11 - Updating node table
    • Step 12 - Verifying Product Dependencies
    • Step 13 - Importing vbulletin-style.xml
    • Template Group: Admin
    • Template Group: BB Code
    • Template Group: Blog
    • Template Group: Blog Admin
    • Template Group: Color
    • Template Group: Content
    • Template Group: Conversation
    • Template Group: CSS
    • Template Group: Display
    • Template Group: Editor
    • Template Group: Error
    • Template Group: Group
    • Template Group: Human Verification
    • Template Group: Inline Moderation
    • Template Group: Link
    • Template Group: Login
    • Template Group: Media
    • Template Group: Modify
    • Template Group: Pagenav
    • Template Group: Photo
    • Template Group: Picture
    • Template Group: Private Message
    • Template Group: Profile
    • Template Group: Screen Layout
    • Template Group: Search
    • Template Group: Group Admin
    • Template Group: Subscription
    • Template Group: Tag
    • Template Group: User Profile Field
    • Template Group: User Setting
    • Template Group: Widget
    • Template Group: Ungrouped Templates 1
    • Template Group: Ungrouped Templates 2
    • Template Group: Ungrouped Templates 3
    • Template Group: Ungrouped Templates 4
    • Template Group: Ungrouped Templates 5
    • Template Group: Ungrouped Templates 6
    • Step 13 - Import Done
    • Step 14 - Reseting cache
    • Step 15 - Skipping step, not needed
    • Step 16 - Import the password schemes

    Status: Aborted



    The specific error message was as follows:

    Unexpected Text:
    <?xml version="1.0" encoding="windows-1252"?>

    Please note that I have received very similar error messages with every upgrade since version 5.0.0. I'd really like to get this resolved and hope the vBulletin team can help. Not a single upgrade since 5.0.0 has worked all the way to 100%. Let's try to get this fixed... I am willing to try anything.

    thanks,
    Kelly
    kelly's red beet factory, www.redbeet.com

  • #2
    Also, now I can no longer reply to any existing threads, and I'm the administrator! The "post reply" button is simply GONE. I haven't checked yet if regular users have the same problem too. My forum is pretty slow and can go several days without a post.
    kelly's red beet factory, www.redbeet.com

    Comment


    • #3
      Has the upgrade now completed? Things may not work if it hasn't.
      Refresh the upgrade screen and see if it continues.
      MARK.B | vBULLETIN SUPPORT

      TalkNewsUK - My vBulletin 5.5.2 Demo
      AdminAmmo - My Cloud Demo

      Comment


      • #4
        No, the upgrade has not completed. Running it again fails at the same spot. Why would you think it's now completed? Nothing has changed, it aborts at the same place.
        kelly's red beet factory, www.redbeet.com

        Comment


        • #5
          No help at all for me?! I wish I'd stuck with vBulletin 4.x. :-(
          kelly's red beet factory, www.redbeet.com

          Comment


          • #6
            I've opened a support ticket for you, please follow up with it ASAP so we can get this resolved.

            Comment


            • #7
              Keeping a close eye on this. I want to upgrade my forums for 5.1.0 but am really afraid to experiment with the latest version. What is the experiment fails ? Its a risk that I do not want to take. Please post an announcement when the 5.1.0 version is stable. I deeply desire and wish to upgrade but certainly not at the cost of losing the business altogether.

              No a side note :
              Why isn't there any auto-update functionality ? Will there be ever any ? I migrated from BBPress to Vbulletin thinking it was the best, lol.

              Comment


              • #8
                I'd take a backup and go for it, in all of our testing this is the only time I've ever seen or heard that someone was having issues upgrading.

                Comment

                Related Topics

                Collapse

                Working...
                X