Upgrading 4.2.3 to 4.2.5 Failed with "Unable to find Type : vBForum_IPAddress"

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • Sergio61
    Member
    • Nov 2018
    • 34
    • 4.2.x

    Upgrading 4.2.3 to 4.2.5 Failed with "Unable to find Type : vBForum_IPAddress"

    I want to move my forum to a

    VPS with Ubuntu 16.04
    PHP 5.6 & PHP 7.0 installed
    MySQL 5.7
    Forum 4.2.3

    What I did (with PHP 5.6):

    1. Downloaded the files from the FTP
    2. Put them on the new FTP server
    3. Downloaded the database
    4. Imported in PHPMyAdmin
    - After importing I missed tables like post and users.
    5. I decide to start the upgrade and uploaded the content of the "upload" folder.
    6. The upgrade didn't finish because of the error:
    At step 7 of the upgrade, it comes with the error:
    • Step 7 - Upgrade Aborted : Unable to find Type : vBForum_IPAddress
    7. I was able to enter the forum
    8. Decided to copy the missing tables to the new database.
    9. I was able to see the old posts and users.
    10. My forum hangs at 4.2.5 Beta 1 at this moment. I don't know what to do. Accessing the forum is not a problem, but when I try to write a post it says "database error" (where can I check the error exactly?), when I try to edit a post I get the error:

    Invalid %1$s specified. If you followed a valid link, please notify the administrator.



    I don't know what to do now. What is the best practice to move my forum? Why didn't the import succesfully import the table post / users and other largest tables and skipped them? I don't have a limit for importing.
    All the limits are changed in the php.ini file.
    Last edited by Sergio61; Thu 8 Nov '18, 1:51am.
  • Mark.B
    vBulletin Support
    • Feb 2004
    • 24286
    • 6.0.X

    #2
    You mentioned this:
    "- After importing I missed tables like post and users."

    There is no point proceeding with an upgrade at that point because your database is clearly incomplete.

    You need to make sure you have a verifiably complete database in place.
    MARK.B
    vBulletin Support
    ------------
    My Unofficial vBulletin 6.0.0 Demo: https://www.talknewsuk.com
    My Unofficial vBulletin Cloud Demo: https://www.adminammo.com

    Comment

    • Sergio61
      Member
      • Nov 2018
      • 34
      • 4.2.x

      #3
      Hello Mark,

      Forgot to mention that I have imported all the tables one by one and still got the same error.

      Comment

      • Mark.B
        vBulletin Support
        • Feb 2004
        • 24286
        • 6.0.X

        #4
        Really you need to have the entire database reimported, and then verify that the forum works as it is, before running the upgrade.
        The reason is that you now don't know whether you have an upgrade problem, or a database import problem.
        MARK.B
        vBulletin Support
        ------------
        My Unofficial vBulletin 6.0.0 Demo: https://www.talknewsuk.com
        My Unofficial vBulletin Cloud Demo: https://www.adminammo.com

        Comment

        • Sergio61
          Member
          • Nov 2018
          • 34
          • 4.2.x

          #5
          Ok, I am on my way to do as you say.
          But I don't get it why the import skips some tables. Do you have any suggestions about that?

          Comment

          • Mark.B
            vBulletin Support
            • Feb 2004
            • 24286
            • 6.0.X

            #6
            Originally posted by Sergio61
            Ok, I am on my way to do as you say.
            But I don't get it why the import skips some tables. Do you have any suggestions about that?
            That's something you would need to take up with your host - importing databases to servers is outside of our control.
            MARK.B
            vBulletin Support
            ------------
            My Unofficial vBulletin 6.0.0 Demo: https://www.talknewsuk.com
            My Unofficial vBulletin Cloud Demo: https://www.adminammo.com

            Comment

            • Wayne Luke
              vBulletin Technical Support Lead
              • Aug 2000
              • 73981

              #7
              This would happen if you didn't run the upgrade scripts that come with vBulletin 4.2.3 and higher. How IP Address is handled was changed in vBulletin 4.2.3.
              Translations provided by Google.

              Wayne Luke
              The Rabid Badger - a vBulletin Cloud demonstration site.
              vBulletin 5 API

              Comment

              • Sergio61
                Member
                • Nov 2018
                • 34
                • 4.2.x

                #8
                This is solved. changed my server from ubuntu 16.04 to 18.04 and started over with mariadb database.

                Comment

                Related Topics

                Collapse

                Working...