The sync engine server is a great place to start because we can easily see data sync errors, the state of the Metaverse object(s), and that of the connector space object(s). The quickest way to know whether the sync engine is experiencing errors is to look at Operations Tool. If a run profile returns a status of anything other than success, then there is an error, such as shown here:

If you click on the row containing the error, the lower pane is split into a statistics window and an error window. With a few exceptions, the error window will contain a hyperlink to the object reporting an error, which you can click on and receive more information:

Another method to identify and work through problems is to search the Metaverse or the connector space directly. We have already discussed how searching using the Metaverse Search tool should be intuitive. Let's look at troubleshooting as its typically done: from the point of the object having issues or at the connector-space level.

To search the connector space, go to the Management Agents tool of the appropriate Management Agent. In our example scenario, the object having an error is an AD object not being updated, so we will click on the AD Management Agent, click on the Search Connector Space icon (or right-click and select Search Connector Space), then enter the object's DN, and finally click on the Search button:

In this situation, we can see that the object is showing as a False connector, meaning it is a disconnector (not connected to a Metaverse object). As the object is not connected to a Metaverse object, it makes sense that data is not flowing to it. Select the object and then click on the Properties button to view the object's connector space data:

There's nothing out of the ordinary in this first view; the object has a display name, employee ID, and other bits of data. Let's look at the Synchronization Error tab in the following screenshot:

The ambiguous import flow from multiple connectors tells us that the attribute we are using for joins has the same value on more than one object. Recall that our join rules in AD are to join on the employee ID, so there are two AD objects with the same employee ID. If we were to search the Metaverse for Amber's employee ID, 10001018, you will notice that another AD object out there exists with the same ID:

The solution is determined on which AD account should be used. If the end user should use the provisioned AD account that is currently joined to the Metaverse, then you would direct the end user to this account and clear the employee ID value on the other account (or delete it). If the disconnected AD object should be used—that is, if we provisioned an account for someone that already had an account (this could happen if the account is missing its employee ID at one time)—then we would need to disconnect the AD object from the Metaverse object, clear its employee ID, and then perform a delta import and delta sync on the AD Management Agent. The correct AD account would be joined to the Metaverse, the HR data would need to update the correct AD object, and a business decision would need to be made about the other account, such as disabling or deleting it.