Uploaded image for project: 'Jira Data Center'
  1. Jira Data Center
  2. JRASERVER-65084

"Failed to start JIRA due to a build number inconsistency" when importing a Cloud backup to Server

XMLWordPrintable

      "Failed to start JIRA due to a build number inconsistency" when importing a Cloud backup to Server

      Environment

      JIRA Server 7.3.x, JIRA Cloud

      Steps to Reproduce

      1. Obtain an XML instance backup from JIRA Cloud
      2. Install latest version of JIRA Server
      3. Attempt import of Cloud backup to Server following the steps in Migrating from JIRA Cloud to Server applications

      Expected Results

      Import is successful and JIRA starts normally following the import.

      Actual Results

      The following error message is thrown:

      Failed to start JIRA due to a build number inconsistency.
      The data present in your database is newer than the version of JIRA you are trying to startup.
      Database build number: 100035
      JIRA app build number: 73014
      Please use the correct version of JIRA. You are running: 7.3.3#73014-sha1:d5be8da522213be2ca9ad7b043c51da6e4cc9754

      Workaround

      1. Stop JIRA.
      2. Manually update the jira.version.patched property by directly modifying the database.
        UPDATE propertystring SET propertyvalue = '<server build number>' WHERE propertyvalue = '<cloud build number>';
        

        For example, given the above build numbers:

        UPDATE propertystring SET propertyvalue = '73014' WHERE propertyvalue = '100035';
        
      3. Start JIRA normally.
      4. Test to ensure everything works.

      Notes

      Reference: JIRA Build and Version Numbers Reference

              dcef44641fb6 Sumesh Koppantakath
              nparks@atlassian.com Nathan Parks
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated: