Skip to content

Rolling Back a QIE Upgrade

When QIE runs an auto-update, the launcher preserves the previous WAR in a preUpgrade_yyyyMMdd_HHmmss/ folder in the QIE home directory. If the newer build has to be rolled back, the previous WAR can be swapped back in from that folder.

Only the most recent upgrade is retained

QIE keeps exactly one preUpgrade_* folder at any time. Each auto-update deletes the previous one before writing its own backup. Rollback via this mechanism only covers the last upgrade, not older ones. If a specific past version has to be restored (a two-version-back rollback, or after multiple upgrades have run), obtain that installer from Qvera support and reinstall.

Database schema changes can block a rollback

QIE uses Hibernate hbm2ddl.auto=update, which migrates the schema forward on each upgrade, adding columns and constraints as new versions require them. When the newer build introduced schema changes, the older WAR starts against the migrated schema but is not guaranteed to accept it: expect Hibernate SchemaValidationException or SQLSyntaxErrorException on unknown columns at startup. Snapshot the QIE database before every upgrade so a rollback can also restore the pre-upgrade schema if needed.

Rollback procedure

  1. Stop the QIE service so no processes hold the WAR file open.

    • Windows: net stop QIEService from an elevated command prompt, or use the Service Manager.
    • Linux / Mac: sudo systemctl stop qie.

  2. Locate the backup. In the QIE home directory (-Dqie.home, e.g. C:\ProgramData\QIE or /java/qie) find the most recent preUpgrade_yyyyMMdd_HHmmss/ folder. It contains the previous qie.war and any files QIE replaced during the upgrade.

  3. Copy the previous WAR back into place, overwriting the current qie.war in the QIE home directory:

    • Windows: copy /Y preUpgrade_yyyyMMdd_HHmmss\qie.war qie.war
    • Linux / Mac: cp preUpgrade_yyyyMMdd_HHmmss/qie.war qie.war

  4. If the upgrade included schema changes, restore the pre-upgrade database snapshot from your backup regimen. Skip this step only when you are certain the upgrade was schema-neutral.

  5. Restart the QIE service.

  6. Confirm the version. Sign in and open Help -> About; the Installed Build number should now match the previous version. Also check qieLauncher.log. The QieLauncher version: line at startup shows the launcher's version, which is independent of the WAR.

If startup fails with a Hibernate schema error, the older WAR does not accept the migrated schema, restore the pre-upgrade database snapshot and restart, or roll forward to the newer version until the underlying issue can be addressed with Qvera support.