TPAM Hotfix 8128v2 for Solution 212781 - Locate SyncPassSubscribers rows with orphaned SyncPassID values (4347623)

TPAM Hotfix 8128v2 for Solution 212781 - Locate SyncPassSubscribers rows with orphaned SyncPassID values

This hotfix includes the changes outlined in the following sections. One Identity may generate additional hotfixes for future releases of the product.

The minimum version for installing this hotfix is 2.5.915.

Resolved Issue: Locate SyncPassSubscribers rows with orphaned SyncPassID values. Updated/removed values will appear in patch log and TPAM activity log.

Revision Information: The difference between hotfix 8128, which was released in March 2016, and hotfix 8128v2, is that 8128v2 adds an additional step to make sure the AcctAutoFl is properly set for subscribers. Also hotfix 8128 could only be applied to TPAM 2.5.915. Hotfix 8128v2 can be applied to 2.5.915 - 2.5.918.

Please download the hotfix, TPAM Hotfix 8128v2 for KB 212781, by clicking here.

Resolved issues

The following is a list of issues resolved in this hotfix.

Issues resolved in hotfix 8128v2:

Resolved Issue	Issue ID
Locate SyncPassSubscribers rows with orphaned SyncPassID values. Updated/removed values will appear in patch log and TPAM activity log.	8128
When adding a synchronized password subscriber, receive error "Cannot insert duplicate key row in object 'dbo.SyncPassSubscribers' with unique index 'IX_SynchPassSubscribers'.	9302

Applicability of this hotfix

Products affected by this hotfix:

Product Name	Version
TPAM	2.5.915 - 918

Installing this hotfix

To install the hotfix:

1. Take a backup of the TPAM appliance.

2. Copy the supplied .zip to your local computer.

3. Log in to the TPAM /admin interface.

4. Select Maint | Apply a Patch from the menu.

5. Click the Select File button.

6. Click the Browse button. Select the patch file that you saved locally.

7. Click the Upload button.

8. Type UdwzQjrRXl in the Key box.

9. Type /genkey in the Options box.

10. By default, if you are applying a patch to a primary member of a cluster, the replicas in the cluster will be listed and highlighted in the Target Replicas list. If any of the replicas are deselected, the patch will not be applied to it. The replica can be patched at a later date by logging on directly to the /admin interface of the replica. If the software version numbers (excluding the build number) of the primary and the replica still match them the primary will still be able to send data to the replica. We recommend that you contact Technical Support before deciding to deselect any of the replicas on this list.

11. Click the Apply Patch button.


Verifying successful installation

To determine if this hotfix is installed:

1. Click the Patch Log tab.

2. To set the log refresh interval, select Refresh Results every X seconds.

3. Once the hotfix has been applied there will be a message in the patch log stating “Patch successfully applied to system”.


Removing this hotfix

To remove this hotfix:

1. To remove this hotfix the TPAM appliance can be restored using the backup taken prior to applying the hotfix. We recommend discussing this with Technical Support prior to completing the restore.                          

8128

TPAM_2.5.915_8128_ReleaseNotes