Hi,
We are trying to upgrade to the latest release (1.12.2) from the 1.10.4 version of OSTicket, but we are encountering an error which states "The upgrader does not support upgrading from the current patch" right after we copy the new installation files and login to the scp, the PHP version, MySQLi extension and MySQL version should all be fine, but they are all flagged as wrong, and the upgrade process cannot be started...

Here are the technical infos from the dashboard - > Information page:

  • OSTicket version: v1.10.4 (035fd0a)
  • Web Server: Microsoft-IIS/8.0
  • MySQL version: 5.5.62
  • PHP version: 7.1.19

We've also tried upgrading to the 1.10.7 Maintenance release, but the result was the same...

Thanks for your help

@ripat

Try downgrading to PHP 7.0 or 5.6 and then try to upgrade. Remember, v1.10.4 is not fully compatible with 7.1 and may have issues such as this.

Cheers.

Hi Kevin,
thanks for the reply,
I've tried downgrading to 5.6.31, and the error stays the same...
I've tried upgrading to both 1.10.7 and 1.12.2 with php 5.6.

Thank you very much for your time

18 days later

Hi,

sorry to bump this, but is there anything else I can do to try and solve this issues?

Thanks for your time

Take a look at your \bootstrap.php

What are the lines 316-319?

Take a look at your ost_config table or Run this SQL and tell us the result.

SELECT value FROM ost_config WHERE key='schema_signature';

the lines are the following:
#Current version && schema signature (Changes from version to version)
define('THIS_VERSION', 'v1.10.4'); // Set by installer
define('GIT_VERSION', '035fd0a'); // Set by installer
define('MAJOR_VERSION', '1.10');

while the schema signature in ost_config table is eb3c85b34c05f21bdce7b075f5157929

Well that would be the problem.

schema eb3c85b34c05f21bdce7b075f5157929 is not a valid database schema.
I'll ask a dev what we can do to fix this in your case.

I imagine that we could try putting the schema in for 1.10.0 but want to confirm that. 🙂

Ok, thank you very much, I will wait for your reply 😀

So chances are if you put in the schemea for 1.10.0 that it will break things.
They recommended that you go through all the mysql schema updates and figure out which ones have been run, and which ones have not. And manually run them to bring your DB to current.

The upgrade scripts are located at:
\include\upgrader\streams\core

a month later

Hi!
Sorry, going through all the schema updates took a while,
All the schema updates were run successfully, the problem was in one of the installation schema update (of version 1.10.4), which had a wrong signature, putting in the right one (I first verified that the rest of the file was correct) fixxed everything 🙂
Thank you very much for your help

    2 years later

    ripat Hi Ripat, I'm having trouble upgrading from the same version 1.10.4. How did you run the schema updates and what was the correct signature that you updated? I can't seem to upgrade from 1.10.4 to another version. It always ends in errors. Any help would be appreciated.

      a year later

      hi, if still useful... same situation, I uploaded the 1.11 version (https://master[dot]dl[dot]sourceforge[dot]net/project/sf-osticket/v1.11/osTicket-v1.11.zip?viasf=1), set the schema_signature to 98ad7d550c26ac44340350912296e673
      and worked! Can be also that works directly with 1.16 version

      [edited by admin]

      Write a Reply...