Who is this article for?

Users who encounter the error when using the Sync Person To LDAP function.

IT Administrator permissions are required to resolve the issue.

If you configure a system to work with LDAP, you can import users and sync their properties with the LDAP records. When synchronising, either through the desktop application or the Robot's SyncLDAP job, you might see this error: "Bindings collection does not contain an item with ID=[some GUID]". This article explains what causes the issue and how to resolve it.

1. Issue
2. Solution

1. Issue

When you configure an LDAP connection, you create a new file at Service\LDAP.config.  This file contains a GUID for each binding.

This GUID is used to create a unique identifier for each Person record you sync.

If you create a new LDAP.config file, or if you update your existing LDAP.config file and delete the binding, then this expected GUID will not be there.

When you try and Sync Person to LDAP or use the SyncLDAP Robot job, the process will fail with the error.

This is particularly likely in a UAT environment, where:

• You sync to LDAP in the Production system.
• You have created a separate LDAP configuration in UAT.
• You have copied the Production database to UAT.

2. Solution

To resolve the issue, ensure that your LDAP.config file has a binding with a GUID at <TngLDAPBinding><ID> that matches the one in place when the Person record was originally synchronised.  This may mean copying the GUID for Production to UAT.

After changing this value:

1. Restart the application pools.
2. Restart the Robot service.
3. Restart App Manager (if it is already open).

Below is a demonstration of the issue and how to resolve it.

https://app.screendesk.io/recordings/a845c3e9-31c7-45ea-aa13-48a1da775414