Skip to main content

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.

Note:

A special upgrade procedure is required when upgrading from Health Connect 15.03. For details, see the InterSystems IRIS In-Place Conversion Guide, which is available from the InterSystems WRC DocumentsOpens in a new tab page.

MPRLLIB Database

Affects Upgrades From Versions:

All versions.

Conditions:

HealthShare Health Connect and InterSystems IRIS for Health users who previously migrated from Health Connect/HSAP based on the Caché/Ensemble platform.

Ramifications:

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.

Instructions:

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

Affects Upgrade From Versions:

2022.3 and earlier.

Conditions:

All environments. Environments with active configuration in the Configure SSL Access dialog must perform additional steps.

Ramifications:

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.

Instructions:

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

Affects Upgrades From Versions:

2022.1.5 and earlier.

Conditions:

Instances running on Windows.

Ramifications:

The irisstop.exe file is removed upon upgrade. Without this file, you cannot stop the HealthShare® Health Connect instance using any internal means. For example, the iris stop command does not work.

Instructions:

To permanently address this problem:

  1. 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 Health Connect (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/.

  2. Proceed with your upgrade as usual.

  3. After upgrading, add the copy of the irisstop.exe file to the upgraded instance.

  4. On the upgraded instance, execute the file: <install-dir>/InterSystems/<instance-name>/bin/iristray.exe.

  5. Open the Health Connect launcher menu for the upgraded instance, then click Exit.

  6. 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 Health Connect instance manually, using the Services Windows Administrative Tool. Open Services and right-click on the Health Connect Controller for <instance-name> service, then click Stop.

Recompile Classes Featuring Properties with MAXLEN=""

Affects Upgrade From Versions:

2022.1.1 and earlier.

Conditions:

Environments with existing classes containing a property with MAXLEN="".

Ramifications:

If an existing class contains a property with MAXLEN="", SQL queries on tables based on that class return an error after upgrading.

Instructions:

Recompile the affected classes.

C Runtime Requirements on AIX®

Affects Upgrade From Versions:

2021.2 and earlier.

Conditions:

Environments running on AIX®.

Ramifications:

Health Connect on AIX is compiled using the IBM XL C/C++ for AIX 16.1.0 compiler.

Instructions:

If the system on which you are installing InterSystems IRIS for Health does not have the corresponding version of the runtime already installed, you must install it.

Durable %SYS

Affects Upgrade From Versions:

2019.2 and earlier.

Conditions:

Environments using a durable %SYS from a 2019.2 or earlier release.

Ramifications:

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.

Instructions:

Please contact your InterSystems sales engineer or the InterSystems Worldwide Response CenterOpens in a new tab for instructions on changing the relevant file ownerships.

FeedbackOpens in a new tab