No announcement yet.

Upgrading from 4.1.3 to 4.2.0 Database error

  • Filter
  • Time
  • Show
Clear All
new posts

  • [Suite] Upgrading from 4.1.3 to 4.2.0 Database error

    Turned off Forum
    Backed up database
    Backed up all files on the server, but left them on the server.
    Uploaded 4.2.0 files, leaving OLD 4.1.3 config.php in place.
    Go to and get this message:

    Click image for larger version

Name:	Upgrade Error.JPG
Views:	1
Size:	35.3 KB
ID:	3724084

    My e-mail address is correct in config.php, but I receive no e-mail with details of the error.
    How do I figure out what is wrong?


    - - - Updated - - -

    some more info...

    I've been doing upgrades for years, and never encountered this problem.
    Until I uploaded the 4.2.0 files I had no problems with the forum. The only thing I've done is upload the files.
    I've double-checked my config.php and it still has the correct database, username, password, e-mail, etc.

  • #2
    Did you run the upgrade yet?


    • #3
      No. Only went to the upgrade url. Can't get past there.

      I'm uploading my backup now so I can get the forum running again until I figure out what went wrong.

      the upgrade went fine on the test forum.


      • #4
        Well before you do that, edit your config.php file and add:

        $config['Misc']['debug'] =1;

        To your config.php file, then refresh the database error page

        FYI you WILL get database errors when you're not running 4.2.0 in the frontend until you complete the upgrade.

        What does the upgrader show?

        Also you never need to change your config file to date, from vB 3.5 to 4.2.0, its more or less the same file (new stuff added).

        When I tried to go to your update page, it redirected me to the index. Which tells me 2 things, a 404 happened and redirected me to the index, or something else happened. The db error page isn't from the upgrader.


        • #5
          You know what - I'm an idiot. the url should be not!

          gonna stop the upload and re-up the 4.2.0 and try again.

          I'm such an idiot!


          Related Topics