When the upgrade is interrupted during the pre-install phase, the installer exits without triggering a rollback. Because no installation changes are applied at this stage, the previously installed server version remains intact. However, some preparatory actions, such as prerequisite checks may have completed. The database is not affected.

To resume the upgrade that is interrupted during the pre-install phase, complete the following steps:
  1. For a standalone server or the primary server in a high‑availability deployment, verify that the MongoDB binaries directory is present at:
    • Windows: <OECC-install-dir>\database\MongoDB\bin
    • Linux: <OECC-install-dir>/database/MongoDB/bin
    Note: Skip this step for the secondary server in a high‑availability deployment.
    If the directory is... Present

    Present

    		 Go to step 2.

    Not present

    Restore the database from the backup directory, and then proceed to step 2. For information about restoring the database, see Restore OpenEdge Command Center database.
  2. Relaunch the installer and proceed with the upgrade. For details, see Upgrade OpenEdge Command Center server.