--- title: Troubleshooting a multiple correlation entry error description: For environments that use correlated Lightweight Directory Access Protocol (LDAP) data views with the System for Cross-domain Identity Management (SCIM) 2.0 implementation, the SCIM response can include an error if multiple entries have a secondary correlation attribute value that matches the primary correlation attribute value. The error is applicable to both PingDirectory and PingDirectoryProxy. component: pingdirectory version: 11.1 page_id: pingdirectory:managing_scim:pd_ds_troubleshoot_correlation_error canonical_url: https://docs.pingidentity.com/pingdirectory/11.1/managing_scim/pd_ds_troubleshoot_correlation_error.html llms_txt: https://docs.pingidentity.com/pingdirectory/llms.txt docs_for_agents: https://developer.pingidentity.com/build-with-ai/docs-for-agents.md revdate: 2026-08-17T00:00:00Z page_aliases: ["managing_scim_11_and_20_servlet_extensions:pd_ds_troubleshoot_correlation_error.adoc"] --- # Troubleshooting a multiple correlation entry error For environments that use correlated Lightweight Directory Access Protocol (LDAP) *(tooltip: \
\

An open, cross platform protocol used for interacting with directory services.\

\
)* data views with the System for Cross-domain Identity Management (SCIM) *(tooltip: \
\

An application-level, HTTP-based protocol for provisioning and managing user identity information. SCIM supplies a common schema for representing users and groups and provides a REST API.\

\
)* 2.0 implementation, the SCIM response can include an error if multiple entries have a secondary correlation attribute value that matches the primary correlation attribute value. The error is applicable to both PingDirectory and PingDirectoryProxy. There are three options for resolving this error: * Configure one or more correlation attribute pairs on the correlated LDAP data view so that for each primary entry, there is only one other entry with matching secondary correlation attribute values. This is the recommended option. * Modify the server data so that for each primary entry, there is only one other entry with a matching secondary correlation attribute value. This option isn't efficient for larger servers because it requires making changes to individual entries. * If the other options don't resolve the issue, remove the correlated LDAP data view.