Premier | Self-Update Post Version 2.13

Premier | Self-Update Post Version 2.13

🔍 Summary

From version 2.13.7 onwards, Core clients can now self-update directly from the Launcher application. This process ensures your Premier Core system stays current while automatically handling backups and database updates.


❓ Likely Scenario

  • Your system is running an older version and an update is available.

  • IT support needs to perform a version upgrade on the LIVE or TRAINING environments.

  • An update process has failed and requires retrying.

  • You need to confirm whether your database and application files have updated correctly.


🛠️ Process Overview

The update process is handled through the Launcher (Premier LIVE/Core LIVE) on your APP server. The system will back up your database and application files, download the latest update, and then apply schema and application updates to both LIVE and TRAINING environments. The update wizard will guide you step by step, and if errors occur, it will either roll back or allow retry after correcting service issues.

​

✅ Step-by-Step Instructions:

  1. Prepare for Update

    • Ensure you are already on Premier Core Software version 2.13.

    • Log out all users from the application.

    • Stop the Premier Interface Poller (if using PMS integration).

    • Confirm you have sufficient disk space (double the size of your database).

    • Verify internet access to https://premiersoftware.uk.


  1. Launch the Update

    • On your APP server, open the Launcher (Premier LIVE/Core LIVE).

    • The system will check for updates. If one is available, click Yes.

    • (Optional) View release notes before proceeding.

  2. Download and Install

    • The update will download and extract to the Temp Directory.

    • Select the correct installation (e.g., PremierSoftware_SERVER).

    • Confirm the version and environments (LIVE and TRAINING).

    • Click Finish to begin the upgrade.

  3. Update Steps

    • Step 1/3: Backup database and application files.

    • Step 2/3: Perform pre-update checks.

    • Step 3/3: Apply database schema updates and update application files.

    • If errors occur, stop the Premier Platform Service and PMS interfaces, then click Retry.

  4. Finalise Update

    • Once complete, the updater will finish and restart services.

    • The CRM system will be notified of the update (contact support if this fails).

    • Relaunch the software on the server to run the Client Update.

    • Confirm the new version number on the Launcher.

    • Restart PMS Interface Services if applicable.

    • On client machines, open the software to download updated files.

🧠 Important Note

Notes
  • Always ensure backups are taken before updating (handled automatically during Step 1).

  • Errors during update often result from services restarting—verify Premier Platform Service and PMS interfaces are stopped before retrying.

  • Update failures due to disconnected users can be resolved by ensuring all applications are fully closed.

  • If CRM notification fails, contact Journey Support to update manually.

🔗 Related Articles