Skip to content
Effettua una ricerca per conoscere i prodotti e le soluzioni di InterSystems, le opportunità di carriera e altro ancora.

Advisory: Failure to Access Linkage Engine Libraries in Provider Directory

October 15, 2020 – Advisory: Failure to Access Linkage Engine Libraries in Provider Directory

InterSystems has corrected an issue that may occur in certain UNIX environments running Provider Directory.

This problem exists for Customers who use one of the following versions:

  • HealthShare Provider Directory 2019.1, 2020.1 running on UNIX platforms

This issue is limited to UNIX platforms that fail to load the linkage engine libraries on initial start-up. The problem appears to be limited to systems that are running on underpowered environments, such as test systems.

Linkage evaluations and linkage rebuilds may receive errors attempting to access the linkage engine library. These errors show up in the error log, and users can query to see if these errors have occurred in their environment.

To resolve this issue customers are advised to stop and restart the installed instance.

The correction for this defect is identified as SOH723 and will be included in all future product releases. It is also available via Ad hoc change file (patch) or full kit distribution from the Worldwide Response Center (WRC).

If you have any questions regarding this advisory, please contact the WRC.

RELATED TOPICS

Latest Alerts & Advisories

07 Oct 2025
Risk Category & Score Explicit Requirements HSHC-5268 HealthShare® Health Connect and InterSystems IRIS® for Health versions 2025.1.1 Functional: Medium Risk Occurs when performing SDA3 -> FHIR transformations involving the Encounter resource.
07 Oct 2025
Risk Category & Score Explicit Requirements DP-442892 InterSystems IRIS® data platform InterSystems IRIS® for Health HealthShare® Health Connect versions 2023.3.0, 2024.1.0 – 2024.1.3, 2024.2.0, 2024.3.0, and 2025.1.0 HealthShare® Unified Care Record versions 2024.2 and 2025.1 Wrong Results: High Risk Specific use of OUTER JOIN when the inner leg has an index on the join fields In InterSystems IRIS versions 2023.3.0, 2024.1.0 – 2024.1.3, 2024.2.0, 2024.3.0, and 2025.1.0, for queries that use an OUTER JOIN and where InterSystems IRIS performs parallel execution, the query may silently return wrong results.
07 Oct 2025
Risk Category & Score Explicit Requirements DP-443396 InterSystems IRIS® data platform InterSystems IRIS® for Health HealthShare® Health Connect versions 2024.1.0 – 2024.1.4, 2024.2.0, 2024.3.0, and 2025.1.0, and 2025.1.1 HealthShare® Unified Care Record versions 2024.2 and 2025.1 Wrong Results: Low Risk Using Common Table Expressions in Dynamic SQL
30 Sep 2025
In InterSystems IRIS, InterSystems IRIS for Health, and HealthShare Health Connect, versions 2025.1.1 and 2025.2.0, the new “ Mirror Database Download” functionality does not include certain globals.
24 Sep 2025
Risk Category & Score Explicit Requirements DP-444551 InterSystems IRIS® data platform InterSystems IRIS® for Health HealthShare® Health Connect versions 2025.1.0, 2025.1.1, and 2025.2
03 Sep 2025
Risk Category & Score Explicit Requirements DP-442440 InterSystems IRIS ® data platform 2025.1.1.308.0 InterSystems IRIS for Health HealthShare® Health Connect Operational:
23 Jul 2025
InterSystems IRIS 2025.2 introduces the IRISSECURITY database, the new home for security data. Unlike IRISSYS, the previous home for security data, IRISSECURITY can be encrypted, which secures your sensitive data at rest. In a future version, IRISSECURITY will be mirrorable.
23 Jul 2025
InterSystems is pleased to announce the General Availability (GA) of the 2025.2 release of InterSystems IRIS® data platform. This is a Continuous Delivery (CD) release. Please note that the GA versions of InterSystems IRIS for Health™ and HealthShare® Health Connect™ 2025.2 are currently withheld due to mirroring limitations introduced by security updates (details below).
10 Jun 2025
Advisory ID Product & Versions Affected Risk Category & Score Explicit Requirements DP-439649 Products:
20 May 2025
This issue affects all versions of HealthShare®: