Overview
It is possible that for some reason the upgrade process stops before the process has finalized everything leaving some of the settings to wrong value preventing subsequent upgrade attempts. This article will explain one possible scenario and a way to fix it.
Sample Case
In this example scenario we were making the M-Files version upgrade for two servers (app and proxy).
Update was fast and successful for the app server where the actual vault is located, but when updating the version for proxy server it failed.
The failure at first place was since the customer's new M-Files license wasn't installed to the M-Files server and the current license was due. After installing a new license update was run again.
The update failed. The updating process got stuck on Setup window and showing "Activating M-Files Desktop.." state, this window was there a while until the operation returned timeout.
In this case there was error recorded in Windows event log:
Error 1722. There is a problem with this Windows Installer package. The program run as part of the setup did not finish as expected. Contact your support personnel or package vendor. Action activate_server, location: C:\folder\M-Files\24.11.14245.5\Common, command: "C:\ folder\M-Files\24.11.14245.5\Bin\x64\Activator.exe" -a /server
Cause and Reason
The interrupted installation process failed to finish operation correctly and couldn't remove all the references or files about newer version of the M-Files when the upgrade failed as it was trying to roll back to the previous version.
This caused a new attempt to fail as it could not proceed further with wrong settings in the IIS.
Solution
Failed upgrade had created a new Application pool "M-Files 24.12.14341.6." for IIS and all the M-Files related sites were referring for that instead of the older M-Files 24.5. version that was being used. Once created a new application pool and changed all the sites to refer that instead of "M-Files 24.12.14341.6." and deleted pool "M-Files 24.12.14341.6." the upgrade was successful. Also make sure that there aren't any other references to the newer version anywhere before upgrading.
