Upgrade Notes 

If you have your own installation of Estate Manager which is not managed by Irisys, and you want to update it to the latest version, these are the instructions you’re looking for.

For installing a new instance of Estate Manager, see separate guide, here. The instructions below are for upgrades only.

Do NOT blindly run the Estate Manager installer. You must follow the instructions below, or the upgrade will fail.
If you are running an older version of Estate Manager on server 2016, or 2012 R2 you must update it to Server 2019 before upgrading Estate Manager. Note that 2012 was never supported.
Windows Server 2019 is strongly recommended going forward.

Before proceeding, if you have installed any additional software on your Estate Manager server, be advised that there may be issues with Estate Manager or the other software following an upgrade.

Note that Irisys will not be able to assist with upgrade issues arising from having additional software running on the EM server.
In all cases, Estate Manager should run on its own dedicated hardware.

 

Pre-requisites

Before you start an upgrade, make sure you have the required installation files downloaded from the Irisys partner portal and available for use on the server (not on a network share).

Also ensure you have backed up all your data and are fully acquainted with the restore process – just in case it is required if something goes wrong later.

You will also need to know the user details that the services run under, as well as the details of the Database server where the Estate Manager Database is located, plus the admin user account details for that server. Be sure to have this information before proceeding.

IMPORTANT: Estate Manager upgrades must be performed via the user account who originally installed EM.
IMPORTANT: This upgrade will not work on very old versions of Estate Manager. A minimum version of 1.4.7.1 is required, please contact Irisys for additional guidance and instructions if you are running an older version.

 

Upgrade Instructions

1. Ensure that you have backed up your data before proceeding.

2. Manually run Windows Update and ensure that all ‘Required’ updates are installed, and any significant ‘Optional’ updates are also installed.

3. Check the optional updates list and select the .Net version 4.8 entry if it is available.

4. After installing updates, a restart is usually required, do this before continuing.

5. Now stop all of the Estate Manager Services.

6. Once the services have been stopped, go to Windows ‘Add/Remove programs’, locate Estate Manager in the list, select it and click ‘Uninstall’.

7. Once that is complete, reboot the server.

8. Using ‘Add/Remove programs’ again, Uninstall ‘RabbitMQ’ and ‘Erlang’.

9. Reboot the server again.

10. Now locate and manually delete the folder: c:\users\<username>\appdata\roaming\RabbitMQ

11. It is important that a minimum version of .Net 4.8 Runtime files are installed before the main installation can begin, so open the Windows ‘Add/Remove programs’ and look for .Net in the list. If it is older than 4.8, first manually update by double clicking the file:  ndp48-x86-x64-allos-enu.exe

12. Perform another reboot if prompted.

13. The main installation can now begin. First, install the new version of ‘Erlang’ by double clicking the file:     otp_win64_22.1.exe

14. Next, install the new version of ‘RabbitMQ’ by double clicking the file:  rabbitmq-server-3.7.18.exe

15. Reboot the server once more.

16. To begin the main ‘Estate Manager’ install, double click the file: EstateManagerSetup.exe

17. Don’t change any of the details for what user the services run under.

18. Enter the details of the DB server where the EM Database is located along with the admin user for the DB server.

19. Enter ‘localhost’ for the RabbitMQ address and ‘guest’ for the username and password.

20. The installation will then proceed, this may take a while, especially if a database migration is required.

21. At the end of the installation process, a final reboot is required.

If you are using the free SQL version as your main database, you should also consider upgrading to full SQL at this time.