Special Considerations When Upgrading
This page includes special considerations that should be reviewed when upgrading. Each item includes Affects Upgrade From Versions (upgrades from these versions are impacted), the Conditions where the item is relevant, the Ramifications of the item, and any Instructions that should be followed for addressing the item. These instructions supplement Upgrading from an Earlier Version in the Installation Guide.
The considerations are listed from most recent to oldest affected versions. You should review items as far back as the release you are upgrading from before starting your upgrade.
MPRLLIB Database
All versions.
HealthShare Health Connect and InterSystems IRIS for Health users who previously migrated from Health Connect/HSAP based on the Caché/Ensemble platform.
The components.ini file in your installation directory may have a reference to the database MPRLLIB, which is no longer used by the product. This causes a misleading error message in messages.log saying that this database does not exist. This will prevent a misleading error message in messages.log saying that this database does not exist.
Comment out the reference to this database prior to the upgrade by inserting a semicolon at the start of each line.
Example:
;[MPRLLIB]
;Version=15.032.9686
[HSLIB]
Version=2018.1.0
Compatibility_HSAALIB=15.0
Compatibility_HSPILIB=14.0
Compatibility_VIEWERLIB=17.0
New “Configure Secure Communication” Option in the Installer Wizard
2022.3 and earlier.
All environments. Environments with active configuration in the Configure SSL Access dialog must perform additional steps.
The Configure SSL Access dialog in the Installer Wizard has been renamed to Configure Secure Communication. In the new dialog you must now specify an SSL/TLS Configuration in order to make the secure communication settings Active. A default value of HS.Secure.Demo is entered for the SSL/TLS Configuration setting upon upgrade.
If you had an active configuration in the Configure SSL Access dialog before you upgraded, identify the correct SSL/TLS configuration for your instance in the new Configure Secure Communication dialog after you complete your upgrade but before you reactivate your namespaces.
irisstop.exe Removed on Upgrade
2022.1.5 and earlier.
Instances running on Windows.
The irisstop.exe file is removed upon upgrade. Without this file, you cannot stop the InterSystems IRIS for Health instance using any internal means. For example, the iris stop command does not work.
To permanently address this problem:
-
Obtain a copy of the irisstop.exe file. The easiest way to do this is to copy the file from the instance before upgrading.
-
You can copy the irisstop.exe file from any 2019.1 or newer instance.
-
If you do not have a suitable instance, you can install a temporary instance of InterSystems IRIS for Health (including version 2024.2) and copy the irisstop.exe file from it.
-
By default, the file is located in <install-dir>/InterSystems/<instance-name>/bin/.
-
-
Proceed with your upgrade as usual.
-
After upgrading, add the copy of the irisstop.exe file to the upgraded instance.
-
On the upgraded instance, execute the file: <install-dir>/InterSystems/<instance-name>/bin/iristray.exe.
-
Open the InterSystems IRIS for Health launcher menu for the upgraded instance, then click Exit.
-
Using the Windows Start menu, launch the instance by clicking the application: Launcher [<instance-name>].
Before performing the above steps, you can still stop the InterSystesm IRIS for Health instance manually, using the Services Windows Administrative Tool. Open Services and right-click on the InterSystems IRIS for Health Controller for <instance-name> service, then click Stop.
Recompile Classes Featuring Properties with MAXLEN=""
2022.1.1 and earlier.
Environments with existing classes containing a property with MAXLEN="".
If an existing class contains a property with MAXLEN="", SQL queries on tables based on that class return an error after upgrading.
Recompile the affected classes.
External Language Gateway Configurations
2022.1.1 — 2021.1.0
Environments where all external language gateway configurations have been removed.
You may encounter validation errors during the upgrade process.
To prevent these errors, add a single gateway configuration of type Remote that points to the local gateway with an arbitrary port number. For example, you can set the Server Name / IP Address to 127.0.0.1 and set the Port to 1, naming it ForUpgrade. This can be done at any point prior to upgrading and will not impact normal system operation. This configuration can be deleted after the upgrade is completed.
Durable %SYS
2019.2 and earlier.
Environments using a durable %SYS from a 2019.2 or earlier release.
In this release, the distribution container has a nonroot default user. This improves the security of your container. Some file ownerships in the host’s durable directory must be changed before running this version of InterSystems IRIS. If you do not make these changes, the container will encounter an error starting InterSystems IRIS.
Please contact your InterSystems sales engineer or the InterSystems Worldwide Response CenterOpens in a new tab for instructions on changing the relevant file ownerships.
