System script fails to compile with .NET framework version 4.6.2 and later (255557)

This hotfix includes the changes outlined in the following sections. One Identity may create additional hotfixes for other releases of the product. This hotfix provides updated scripts to fix a compilation error with .NET Framework 4.6.2 and later.

Database compilation fails on system scripts which have code like the following:

.ToHashSet(StringComparer.OrdinalIgnoreCase)

E.g.:

"The following scripts contain errors:

ADS_GetITShopProductOwner

DPR_getColumnsHandledByWorkflow

SPO_GetITShopProductowner_SPSGroup

Do you want to block them?"

.NET framework version 4.6.2 ships its own ToHashSet() extension method which collides with One Identity Manager's own implementation which has the same signature.

At the time of writing, Development has tested this issue against .NET Framework 4.6.2 and later. However, if earlier .NET framework versions receive the same method with the same signature through any updates that Microsoft provides, the issue may also occur in earlier .NET framework versions.

This is a product defect (29896).

Development has replaced all occurrences in the standard scripts with new HashSet(Of String)(enumerable, StringComparer.Ordinal).

The fix will be included with 7.0 SP5, 7.1 SP4, 8.0 SP2 and 8.1.

Updated Items

The following is a list of items updated in this hotfix.

For 7.0.x

Please download the hotfix by clicking here.

For 7.1, 7.1.1, 7.1.2 and 7.1.3

Please download the hotfix by clicking here.

Additionally, we created a patch for the 7.1.3 installset which you can download here. To use the installset patch, extract the archive’s content into the installset root.

For 8.0 and 8.0.1

Please download the hotfix by clicking here.

Additionally, we created a patch for the 8.0.1 installset which you can download here. To use the installset patch, extract the archive’s content into the installset root.

Installing this hotfix:

For general information on installing a hotfix please refer to this Knowledge Base article:

Removing this hotfix

1. Use the backups you have created to restore the original state of the VB.NET scripts.