Announcement

Collapse
No announcement yet.

Upgrade problem

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

  • hotch
    replied
    I don't have it on this computer, but I got a response this morning that since I'd taken care of it, it was being closed.

    Leave a comment:

  • Steve Machol
    Former Customer Support Manager

  • Steve Machol
    replied
    What's the issueid of your support ticket? The only ones that could possibly take that long are ones dealing with import issues that requires jerry's attention, and he doesn't work on weekends.

    Leave a comment:


  • hotch
    replied
    Yes, I did get an email after I submitted it, and No, I never received a response, but nevermind. i ended up importing into phpbb, then importing back into vb

    Leave a comment:

  • Zachery
    Former vBulletin Support

  • Zachery
    replied
    If you filled out a ticket on friday its surely been responded too, did you get an email after you submitted the ticket?

    Leave a comment:


  • hotch
    replied
    yep, i've done all that, and filed the ticket on friday, still haven't heard back

    Leave a comment:

  • Floris
    Senior Member

  • Floris
    replied
    At first glance, nothing obvious that is causing this.


    All I can say now (with having no access or the possibility to try stuff out on your database/server):

    * Make sure the pre-upgrade version is 100% working backup.
    * Make sure all the older file versions are removed from the server (just keep the mysql database there)
    * Make sure all the files (except images) are uploaded in ASCII as transfer mode by the ftp program
    * Make sure you are running only install/upgrade.php and not install/upgrade1.php (upgrade.php will choose it by itself when needed)
    * When running upgrade, let each page load 100% and then press next.
    * When pressing next, make sure it is only pressed once, and give it time to load.

    If all that is done (*try again) and the same error pops up, then I advice you to goto the member area and open a new support ticket, explain the situation and include a link to this thread. Also include the details to your forum, server, ftp, phpmyadmin and if possible, shell access. Someone from our staff will try to locate the issue and attempt to resolve it.

    Leave a comment:


  • hotch
    replied
    http://www.climbdown.net/info.php

    Leave a comment:

  • Floris
    Senior Member

  • Floris
    replied
    hotch; could you please provide us a link to your phpinfo ?

    You can make a new phpinfo.php file with this as content:

    PHP Code:
    <?php
    phpinfo
    ();
    ?>

    Leave a comment:


  • hotch
    replied
    yes.

    The upgrade never works, I always get this same error that it's looking for datastore.

    Leave a comment:

  • Zachery
    Former vBulletin Support

  • Zachery
    replied
    Have you restored to a database that had not been touched by the upgrade each time?

    Leave a comment:


  • hotch
    replied
    Yes. Like 15 times. I've tried everything, and nobody on the forums or through support can figure it out.

    Leave a comment:

  • Zachery
    Former vBulletin Support

  • Zachery
    replied
    Have you ever tried running the upgrade before?

    Leave a comment:


  • hotch
    replied
    I'm not sure. I went into the "settings" table and changed it to "2.3.3" in template version there, but it still says "version 3.0.0" at the bottom of every page, and upgrade.php gives me an error that it can't find the datastore table, which it would only look for if it thought it was version 3... would i be able to set it as 2.3.3 anywhere else? why does it still say 3.0.0 at the bottom of each page?

    Leave a comment:

  • Zachery
    Former vBulletin Support

  • Zachery
    replied
    Why would they "think" they are 3.0.0?

    Leave a comment:


  • hotch
    started a topic Upgrade problem

    Upgrade problem

    Well-- as I outlined in another thread, I'm not able to upgrade... i now BELIEVE that this is because my forums think that they are the wrong version (they are 2.3.3, they think they're 3.0.0)-- where in the database can I change this?

Related Topics

Collapse

Working...
X