The majority of synchronization problems involve the connection state of the external servers and the synchronization of the data between the two endpoints. Make sure PingDataSync can properly fail over to another endpoint or server instance if the connection fails on the highest priority external server.

Another factor in troubleshooting synchronization is determining if the distinguished name (DN)distinguished name (DN)DN A name uniquely identifying an object within the hierarchy of a directory tree. and attribute mappings were properly configured and if the information is properly being synchronized across the network. Typical scenarios include checking for any entry failures and mapping issues.


Use the resync tool to validate Sync Classes and data mappings from one endpoint to another. The tool provides a dry-run option that verifies data operations without actually affecting the data.

While many PingDataSync issues are deployment-related and are directly affected by the hardware, software, and network structure used in the synchronization topology, most failures usually fall into one of the following categories:

Entry Already Exists
When an add operation was attempted on the destination server, an entry with the same DNdistinguished name (DN)DN A name uniquely identifying an object within the hierarchy of a directory tree. already exists.
No Match Found
A match was not found at the destination based on the current Sync Classes and correlation rules (DN and attribute mappingattribute mapping Matching corresponding attributes between an IdP and an SP to identify federated users or add supplemental user information.). When this value has a high count, correlation rule problems are likely.
Failure at Resource
Indicates that some other error happened during the synchronization process that does not fall into the first two categories. Typically, these errors are communication problems with a source or destination server.

Statistics for these and other types of errors are kept in the cn=monitor branch and can be viewed directly using the status command.