Otherwise, we will likely have to uninstall and reinstall our application, which will require a brief downtime. We're wondering if there is any configuration available to us in TeamCity to allow a downgrade. MSI (s) (08:BC) : No System Restore sequence number for this installation. if any exist MSI (c) (14:90) 10:42:10:013: MainEngineThread is returning 1603 Verbose logging stopped. MSI (s) (08:BC) : RESTART MANAGER: Session closed. Installation success or error status: 1603. 1603 means (in principle) another install is in progress. No Couldn’t install message, no hint what to do, no word from the installer. MSI (s) (08:50) : MainEngineThread is returning 1603 This comes up nearly every time Rhino wants to install an update. MSI (s) (08:50) : Deferring clean up of packages/files, if any exist Installation success or error status: 1603. Product Name: Intrigma Scheduling Studio. MSI (s) (08:50) : Windows Installer installed the product.

MSI (s) (08:50) : Product: Intrigma Scheduling Studio - Installation failed. Return value 3.Īction ended 3:09:42: INSTALL.

MSI (s) (08:50) : Product: Intrigma Scheduling Studio - Downgrades are not allowed.Īction ended 3:09:42: LaunchConditions. Here is the relevant text from the install log: The MSI installation failed with error code 1603. Last night we tried to perform a release from our release branch, but it failed because the release was assigned version 3.93, which is lower than version 99.0.248. This release was assigned version 99.0.248, which is very far outside of our normal version control scheme. We recently encountered an issue with one of our deployments, which required us perform a release from our master branch instead of our release branch.

Mainenginethread is returning 1603